Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_types

Read-onlyIdempotent

Find tracked types by searching their name or description with full-text search and relevance ranking.

Instructions

Search tracked types by name or description using FTS5 full-text search with relevance ranking.

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": {
      "search_string": "<search_string>"
    },
    "name": "search_types"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_stringYesSearch string for type name or description (FTS5 full-text search)
include_detailsNoIf false, omit definition_json/description/links for lightweight listing
details_onlyNoIf true, return only id/name + definition_json/description/links

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows it is safe and idempotent. The description adds that it uses FTS5 full-text search with relevance ranking, but no additional behavioral details such as pagination or result limits are disclosed.

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 concise sentence with no redundant information. It front-loads the core purpose and key features (FTS5, relevance ranking), earning every word.

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

Completeness3/5

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

For a simple search tool with good annotations and schema, the description is minimally adequate. However, it lacks details about return format, pagination, or error handling, which would improve completeness.

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?

Schema description coverage is 100%, so the schema already documents all three parameters adequately. The description restates the FTS5 aspect but adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches tracked types using FTS5 full-text search with relevance ranking. It uses a specific verb and resource, distinguishing it from sibling search tools for directives, functions, modules, notes, etc.

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 description implies usage for types by naming them, but does not explicitly state when to use this tool versus alternatives like search_directives or search_functions. No exclusions or context about when not to use are provided.

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