Skip to main content
Glama

Search FitFlow GO help

search
Read-onlyIdempotent

Searches FitFlow GO's public product information and how-to guides for the app. Returns up to 8 results, each with id, title, url and a short snippet. The content is written in Spanish.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords or a short question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond them: a capped result count of 8, the exact field set, and the fact that content is written in Spanish, which matters when constructing a query. It says nothing about what happens with zero matches or how results are ranked.

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?

Three short sentences, front-loaded with the purpose, then the return shape, then the language note. Nothing is redundant or padded.

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?

No output schema exists, so the description must carry the return contract, and it does (count cap plus field list). For a single-parameter read tool this is nearly complete; only empty-result and ranking behavior are left unspecified.

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% and the single 'query' parameter is already documented with length bounds. The description adds no query-syntax or language guidance (e.g., whether to query in Spanish or English against a Spanish corpus), so the baseline applies.

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?

Specific verb and resource: 'Searches FitFlow GO's public product information and how-to guides for the app,' plus the result shape (id, title, url, snippet). Clearly better than a generic 'search' name. It stops short of naming how it differs from the sibling 'fetch' (search-then-retrieve vs. direct lookup), so it is not a 5.

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?

No explicit when-to-use or when-not-to-use statement, and the alternative 'fetch' is never mentioned. Usage is only implied through the corpus scoping ('public product information and how-to guides'), which implies this is for discovery rather than retrieving a known resource.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources