Skip to main content
Glama

Arcgis Branson

by io.github.pipeworx-io

Ask Pipeworx — Grounded

ask_pipeworx_grounded
Read-onlyIdempotent

Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 5,724 across 1497 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_reason:"not_in_source"|"no_tool_match"|"tool_error"|"data_truncated"|"llm_error"} when the data doesn't directly answer. Use whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts (financial verdicts, legal claims, medical lookups, public statements). Costs one extra LLM call vs ask_pipeworx — prefer ask_pipeworx for casual lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
queryNoAlias for question.
promptNoAlias for question.
questionYesYour question in natural language. Accepts query, q, prompt, text, input as aliases.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotations, the description reveals the refusal mechanism, exact success and failure return shapes, refusal_reason enum values, grounding constraint ('using ONLY what the tool result contains'), and the extra LLM call cost. These are material behavioral traits not inferable from annotations.

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 dense but every sentence serves a purpose: mechanism, return contract, usage policy, and cost tradeoff. The critical safety context is front-loaded in the first phrase, and the sibling comparison saves the agent from reading ask_pipeworx's schema.

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

Completeness5/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 fully documents both success and refusal return shapes, including the refusal_reason vocabulary. Combined with strong annotations and explicit usage guidance, nothing essential is missing for correct invocation.

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 coverage is 100%, so the baseline is 3, and the description adds no parameter-specific meaning. The schema already documents the single natural-language question parameter and its aliases; the description's value lies elsewhere.

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 names a specific mode ('Hallucination-resistant answer mode'), states the verb and resource ('EXTRACTS the answer using ONLY what the tool result contains'), and explicitly differentiates it from ask_pipeworx. This leaves no ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: 'Use whenever an answer will be quoted, cited, or acted on,' and names the alternative for casual lookups: 'prefer ask_pipeworx for casual lookups.' It also lists specific high-stakes domains, making tool selection straightforward.

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

All Arcgis Branson toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

All 33 tools have clearly distinct purposes, even those that seem related like ask_pipeworx, ask_pipeworx_grounded, and deep_research are well-differentiated by use case and behavior. Memory tools (remember/recall/forget) and subscription tools (subscribe/unsubscribe/list_subscriptions/recent_alerts) are similarly distinct.

Naming Consistency3/5

All tools use snake_case, but naming patterns are mixed: some are single verbs (forget, recall), some verb_noun (query_layer, search_datasets), some noun_noun (entity_profile, layer_info), and some longer phrases (polymarket_kalshi_spread, scan_competitor_ai_presence). While readable, the inconsistency makes the set feel less coherent.

Tool Count2/5

With 33 tools, the surface is overly broad for a server named after a specific ArcGIS dataset. Many tools are unrelated to the core purpose (e.g., polymarket tools, npm scanning, AI visibility), making the count feel bloated and unfocused.

Completeness2/5

For the stated ArcGIS Branson focus, only 3 tools (search_datasets, query_layer, layer_info) are relevant, offering only read access. The rest are a miscellaneous collection from the Pipeworx ecosystem and other domains, leaving obvious gaps in GIS functionality and no write or analysis capabilities.

Resources