Skip to main content
Glama

toda_init

Create a TODA.md convention file in the current project to standardize capturing deferred issues in a plain-text ledger; reruns are safe and return the convention snippet.

Instructions

Create TODA.md for the current project (idempotent); returns the convention-file snippet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "toda_init"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully volunteers two traits beyond the name: the operation is idempotent and it returns the convention-file snippet. However, it does not say what happens if TODA.md already exists with content (overwrite, merge, or no-op) or how 'the current project' is resolved.

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?

A single sentence with the action front-loaded, followed by the two most decision-relevant facts (idempotency and return value). No filler whatsoever.

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 zero-argument setup tool with no output schema, the description covers what it does, that repeats are safe, and what comes back. The only real gap is where the file lands and what project context is used.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. The description correctly does not invent arguments.

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?

States a specific verb and resource: 'Create TODA.md for the current project'. This is clearly distinct from the sibling operations (add/list/prune/set) without needing to name them, since none of them imply file initialization.

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?

Usage is only implied: 'idempotent' hints that it is safe to call repeatedly or unconditionally, but the description never says when to call this versus toda_add or toda_set, nor whether it is a prerequisite for the other tools.

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