Skip to main content
Glama
Sign In
konbu

konbu

by krtw00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

get_todo

Retrieve complete details of a specific todo by providing its ID, including its description, status, due date, and tags.

Instructions

Fetch the full details of a single todo by ID, including description, status, due date, and tags. Example: {"id":"def67890"} → {"id":"def67890-...","title":"...","description":"...","status":"open","due_date":"2026-06-01","tags":[...]}. Side effects: read-only. Errors if the id does not exist.

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": {
      "id": "<id>"
    },
    "name": "get_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTodo UUID. Short IDs (first 8 characters) are also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • addedInput schema / properties / id / description
      Added value: +"Todo UUID. Short IDs (first 8 characters) are also accepted."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description adds value by explicitly stating 'Side effects: read-only' and 'Errors if the id does not exist'. It also provides an example output, giving sufficient behavioral context for a read operation. Could optionally mention rate limits or caching, but not required.

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?

Three efficient sentences: purpose/fields, example, and side effects/errors. No redundant information, perfectly front-loaded with the core action.

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?

For a simple single-resource fetch tool with no output schema, the description covers input format, what fields are returned via example, and error conditions. It is adequately complete, though adding explicit mention of return type could push it to 5.

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?

Schema coverage is 100% and already documents the 'id' parameter. The description adds that short IDs (first 8 characters) are accepted and provides an example, which is minimal extra value. Baseline 3 is appropriate since schema does most of the work.

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

Purpose5/5

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

The description clearly states 'Fetch the full details of a single todo by ID', which is a specific verb and resource. It lists the fields returned (description, status, due date, tags) and provides an example, making it easy to distinguish from sibling tools like list_todos or update_todo.

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

Usage Guidelines4/5

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

The description implies usage when you have a specific todo ID, and mentions that it errors if the ID doesn't exist. However, it does not explicitly contrast with alternatives like list_todos for fetching multiple todos, leaving a slight gap in when-not-to-use guidance.

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