[FEATURE] Implement the API usage prompt
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start by reading explain_conversion_prompt() and the placeholder api_usage_prompt() in app/mcp/mcp_prompts/converter_prompts.py, then inspect tests/mcp/test_usage_prompt.py. Run that test while implementing the prompt messages and registering api_usage in PROMPT_DEFINITIONS. Done means the prompt is available through MCP and covers API-tool usage, expected inputs, API reference text, and structured answers.
Written by the indexing model from the issue text.
Description
Issue Type
- Bug report
- Feature request
- Documentation update
- Other
Description
Implement the api_usage_prompt() prompt for this project.
This work should include:
- adding the prompt logic in
app/mcp/mcp_prompts/converter_prompts.py - returning prompt messages that help the LLM use API tools correctly
- adding the prompt to
PROMPT_DEFINITIONSwith the nameapi_usage
Why this is needed
The project needs a prompt that tells the LLM how to use API-based tools in a clear and consistent way.
Requirements
- The prompt should explain when to use the API tools
- The prompt should explain what inputs the LLM should look for
- The prompt should use the provided API reference text
- The prompt should help the LLM give clear and structured answers
- The prompt should be available through MCP as
api_usage
Expected outcome
A developer can request the api_usage prompt and get instructions that help the LLM work with the project's API tools.
Additional context
A placeholder function already exists in app/mcp/mcp_prompts/converter_prompts.py:
def api_usage_prompt():
pass
There is also a test file that already references this prompt:
tests/mcp/test_usage_prompt.py
Possible Solution
Follow the same pattern used by explain_conversion_prompt(). The new prompt should return prompt messages and should be added to PROMPT_DEFINITIONS with a clear description.
- Dominant language
- Python
- Stars
- 8
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Robbo-lab/mcp-task-app
-
bug good first issue Test infrastructure v0.0.1
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Robbo-lab/mcp-task-app#110 ·
-
documentation DX good first issue v0.0.1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Robbo-lab/mcp-task-app#109 · 1 comment ·
-
DX enhancement good first issue Test infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Robbo-lab/mcp-task-app#66 · 4 comments ·
-
DX enhancement v0.0.1
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Robbo-lab/mcp-task-app#51 ·
-
bug good first issue v0.0.1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Robbo-lab/mcp-task-app#47 ·
All issues in Robbo-lab/mcp-task-app
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100