Skip to main content
Glama
Sign In

SpecStream

by ai.specstream
OverviewDiscussionsAdmin

Resolve a note

resolve_note

Marks a note done, or reopens it.

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": {
      "expected_version": "<expected_version>",
      "resolved": "<resolved>",
      "note_id": "<note_id>"
    },
    "name": "resolve_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes
resolvedYes
record_idNo
project_idNo
collection_idNo
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Beyond the annotations declaring a non-destructive mutation, the description explains that the operation changes completion state and can later be reversed. It omits the optimistic-concurrency behavior suggested by expected_version, as well as failure and scoping behavior.

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

Conciseness4/5

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

The single sentence is front-loaded and contains no filler. It is efficient, although too terse to cover several invocation-critical details for a six-parameter tool.

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

Completeness2/5

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

For a six-parameter mutation with undocumented parameters and no output schema, the description is insufficient to ensure reliable invocation. The core state transition is clear, but versioning, scoping, and parameter mapping remain unexplained.

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

Parameters2/5

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

With 0% schema description coverage, the description only indirectly suggests that resolved selects between done and reopened, without explicitly mapping its boolean values. It provides no semantics for note_id, expected_version, or the optional record_id, project_id, and collection_id parameters.

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 specifies the operation and resource: marking a note done or reopening it, making clear that resolution is reversible. It does not explicitly differentiate the tool from note-related siblings such as add_note or list_notes.

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 two state changes imply when to use the tool, but there is no guidance on prerequisites, exclusions, or alternatives. The requirement to provide expected_version is particularly important yet receives no usage explanation.

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

All SpecStream toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources