llm_cohere
Send a text prompt to Cohere's language models to generate responses. Specify the model and prompt for tailored results.
Instructions
Send prompt to Cohere
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| prompt | Yes | ||
| model | No | command-r-plus |
Send a text prompt to Cohere's language models to generate responses. Specify the model and prompt for tailored results.
Send prompt to Cohere
| Name | Required | Description | Default |
|---|---|---|---|
| prompt | Yes | ||
| model | No | command-r-plus |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose traits like output format, cost, or rate limits, but it only states the basic action, offering minimal transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (4 words), but it omits essential details, making it under-specified for effective tool use.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 2 parameters, no annotations, and no output schema, the description provides almost no contextual information about behavior, return values, or parameter usage, leaving the agent poorly informed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, and the description does not explain the 'prompt' or 'model' parameters beyond naming 'prompt' in the action, failing to add semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Send prompt to Cohere' clearly identifies the action (send) and resource (Cohere), distinguishing it from sibling LLM tools targeting other providers like Anthropic or OpenAI.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus other LLM providers or alternatives, leaving the agent without context for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GlacierEQ/everything-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server