Skip to main content
Glama

Ask FLX ONE

ask
Read-onlyIdempotent

Plain-language question about the region (what is open tonight, events this weekend, where to eat, local services, moving here). The answer is built only from verified records and guide pages, with every source linked, and says so when the data does not cover it. 15 questions a minute and 300 a day per IP.

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": {
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoTown or county, e.g. "Hornell", "Watkins Glen", "Steuben County"
questionYesUp to 300 characters, e.g. "Who's open for dinner tonight in Hornell?"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantive context beyond that: answers are grounded only in verified records and guide pages, every source is linked, and the tool explicitly reports when the data does not cover the question. It also discloses concrete rate limits (15/minute, 300/day per IP), which no annotation field conveys. The grounded-only claim is consistent with openWorldHint=false.

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

Conciseness4/5

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

Two sentences, front-loaded with the capability and parenthetical scope before the grounding and rate-limit details. Every clause carries information. Slightly dense in the second sentence, where grounding behavior and rate limits are compressed together, but nothing is redundant.

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?

With no output schema, the description correctly describes the return behavior (answer plus linked sources, plus explicit coverage gaps) and supplies operational limits. That is enough for an agent to call it safely and to interpret the response. The remaining gap is the relationship to the structured siblings and the role of the optional town parameter when omitted.

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%, with both parameters documented including a town example list and a 300-character limit, so the schema does the heavy lifting. The description frames the question parameter as plain language about the region, reinforcing that it accepts natural prose rather than identifiers. It adds no guidance on whether 'town' is required, optional, or what happens when it is omitted for county-level questions.

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 states a specific capability: answering plain-language questions about the region, with the domain illustrated by concrete examples (open tonight, weekend events, where to eat, local services, moving here). An agent can tell this is a free-text Q&A entry point rather than a structured lookup. It stops short of a 5 because the examples overlap directly with siblings (open_now, events, search_places) without drawing the line between them.

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?

Topic examples imply the intended use case (open-ended, natural-language questions), and the 300-character question example signals phrasing style. However, there is no explicit 'use this instead of X' guidance and no statement of when the structured siblings should be preferred for the same questions about open-now or events. The overlap is left for the agent to resolve.

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