Skip to main content
Glama

Simap

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent behavior. The description adds valuable detail about returning full schemas with curated examples, ready to call directly, without contradicting 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?

Three sentences front-loaded with purpose, followed by domain examples, return details, and usage guidance. Efficient and well-structured.

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?

Covers purpose, usage context, and return details well. Lacks discussion of error cases or edge conditions, but adequate for a discovery tool with 6 parameters and no output schema.

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 all 6 parameters described (including aliases). The description adds no new semantic detail beyond reiterating the query purpose, so baseline score applies.

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 finds tools by describing data or task, enumerates many domains, and explicitly distinguishes itself as a first-step browsing tool, setting it apart from siblings that perform specific tasks.

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?

Explicitly advises to 'Call this FIRST when you have many tools available and want to see the option set (not just one answer)', providing clear when-to-use and implicit when-not-to-use guidance.

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

All Simap 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
Disambiguation2/5

There are several tools with overlapping query responsibilities: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-variants of the same router, and bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunity discovery. An agent must read the long descriptions carefully to distinguish them, and some variants are behaviorally identical today.

Naming Consistency3/5

All names are readable snake_case, but the verb_noun convention is not consistently applied: some are clean verb phrases like validate_claim and discover_tools, while others are noun phrases like entity_profile, recent_alerts, or simap_project. The prefixed groups (polymarket_*, pipeworx_*) help, but the overall naming style is mixed.

Tool Count2/5

34 tools is above the heavy range, and the set is inflated by redundant router variants, five overlapping Polymarket tools, and loosely related utilities like generate_llms_txt and scan_dependency. The server is named Simap but only three tools relate to Swiss procurement, making the scope feel bloated and misaligned.

Completeness4/5

For an information-retrieval-style server, the core workflows are well covered: discovery, routing, grounded answers, entity resolution, profiles, comparisons, fact-checking, subscriptions, and memory. The main gaps are minor, such as updating a subscription in place or deeper native Simap-specific actions, and those can be worked around.

Resources