Skip to main content
Glama

Get Note

get_note
Read-onlyIdempotent

Retrieve the full text of a DOF note as clean Markdown with metadata and official links. Handles long laws, budgets, and NOMs through paginated results using a character offset.

Instructions

Get the full text of a DOF note as clean Markdown, with metadata and official links.

Long instruments (laws, budgets, NOMs) are paginated: the footer tells you the start value for the next call.

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": {
      "code": "<code>"
    },
    "name": "get_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesNote code (codNota), e.g. 5803775. Returned by the other tools.
startNoCharacter offset to start from, for long notes.
max_charsNoMaximum characters of body text to return.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and open-world, so the safety profile is covered. The description adds value beyond that by disclosing the response shape (Markdown body plus metadata and official links) and the pagination contract for long instruments such as laws, budgets and NOMs.

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 sentences, front-loaded with what is returned, with the pagination caveat second. No filler or repetition of schema content.

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?

A read tool with a full output schema and fully documented parameters needs little more; the description covers output form and pagination behavior. Only the missing routing signal against sibling retrieval tools keeps it short of complete.

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?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning for `start` by explaining that the footer of a paginated response tells you which value to pass next. That pagination loop is not inferable from the schema's bare "character offset" wording.

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?

Names a specific verb and resource ("Get the full text of a DOF note") plus the return format (clean Markdown with metadata and official links). It is clearly distinct from a search tool, though it never names a sibling to sharpen the boundary.

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?

Gives real procedural guidance for the paginated case: the footer supplies the `start` value for the next call. However, it never states when to use this tool versus search_notes or the other retrieval tools, so the selection guidance is only implied.

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