Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

note_get

Retrieve notes attached to a specific item ID to review item context, decisions, or history.

Instructions

Read notes attached to an item id.

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": "note_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
agent_tokenNo
client_agent_idNo
claim_generationNo
client_session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.2
    • addedInput schema / properties / agent_token
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / claim_generation
      Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / client_agent_id
      Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / client_session_id
      Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.1.9

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden, yet it only implies a read via the word 'Read'. It says nothing about authentication (agent_token, client_session_id, claim_generation are all unexplained), whether notes are paginated, or what is returned.

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

Conciseness3/5

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

A single front-loaded sentence with no padding, but that brevity stems from under-specification rather than efficient information density.

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?

No annotations, no output schema, and four fully undocumented parameters make this inadequate for a 5-parameter tool. An agent would have to guess at the semantics of the agent/claim/session fields.

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?

Schema description coverage is 0% across 5 parameters, so the description must compensate and does not. It only lightly clarifies that 'id' refers to an item id; the four agent/claim/session parameters have no explanation anywhere.

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 ('Read') and resource ('notes') scoped to an item id, so the operation is unambiguous. It does not differentiate itself from the close sibling note_list, so an agent cannot tell from the description alone when a single-item read beats a listing call.

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

Usage Guidelines2/5

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

No guidance on when to prefer this over note_list, note_add, or note_update, and no prerequisites or preconditions are stated. Usage is only inferable from the name.

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