Skip to main content
Glama
Sign In
coderide

coderide

by PixdataOrg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_prompt

Fetch the specific prompt or instructions for any task using its unique task number. Get precise context needed for an AI agent to complete the task.

Instructions

Retrieves the specific instructions or prompt for a given task, identified by its unique task number (e.g., 'CRD-1'). This is typically used to understand the detailed requirements or context for an AI agent to work on the task.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "number": "<number>"
    },
    "name": "get_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / number / description
      Removed value: -"The unique identifier for the task (e.g., 'CRD-1'). Must follow the format: three uppercase letters, a hyphen, and one or more digits."
    • changedInput schema / properties / number / pattern
      Previous value: -"^[A-Z]{3}-\\d+$"New value: +"^[A-Za-z]{3}-\\d+$"
  2. First observed

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are absent, so the description must carry the full burden. It only says 'retrieves' but does not state if it is read-only, safe, or if it requires any permissions. There is no mention of side effects or idempotency, which is a notable gap for a retrieval tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with no wasted words. The first sentence defines the tool's primary purpose, and the second provides typical usage context. Information is front-loaded and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only one parameter and no output schema, the description is fairly complete. It explains what the tool does, the input format, and typical usage. However, it could hint at the return value format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for the parameter, but the description clarifies that the parameter is a unique task number (e.g., 'CRD-1') and matches the pattern. This adds some semantic value beyond the schema pattern, but does not fully describe the parameter's purpose or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it retrieves specific instructions/prompt for a task, using a unique task number. It clearly identifies the resource and action, and the example number format helps. However, it does not explicitly differentiate from sibling tools like get_task, which might retrieve task details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'typically used to understand the detailed requirements' which gives some context. But it does not provide when to use vs. alternatives (e.g., get_task) or when not to use it. No exclusion criteria are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools