Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_tracking_notes

Read-onlyIdempotent

Retrieve tracking notes filtered by type, reference, directive, or severity to manage task progress and compliance in functional programming projects.

Instructions

Get tracking notes with optional filters

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

Input Schema

NameRequiredDescriptionDefault
note_typeNoFilter by note_type
reference_typeNoFilter by reference_type
reference_nameNoFilter by reference_name
directive_nameNoFilter by directive_name
severityNoFilter by severity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true, indicating safe, non-mutating behavior. The description adds the concept of 'optional filters' but does not disclose any additional behavioral traits such as result limits, sorting, or performance implications.

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?

The description is a single, clear sentence with no wasted words. It efficiently conveys the core purpose.

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?

Despite having 5 optional parameters, the description lacks details about the return format, pagination, or how this tool differs from similar ones. Given the complexity of the sibling set, more context would be beneficial for correct selection.

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?

With 100% schema description coverage, each parameter already has a 'Filter by ...' description in the schema. The tool description does not add extra semantic information beyond what's in the schema, so the value added is neutral.

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 'Get tracking notes with optional filters' clearly specifies the verb ('Get') and resource ('tracking notes') and mentions filtering capability. However, it does not differentiate from sibling tools like 'get_notes_comprehensive' or 'search_tracking_notes', which may cause confusion about which tool to use.

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?

The description provides no guidance on when to use this tool versus alternatives. Given siblings like 'search_tracking_notes' and 'get_notes_comprehensive', explicit context on when to choose this tool over others is missing.

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