Skip to main content
Glama

Pkg Go Dev

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. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural 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."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds that it returns top-N tools with full schemas and curated examples, ready to call directly, without needing a second lookup.

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?

Description is front-loaded with core purpose and includes a detailed list of domains, which is useful but slightly verbose. Every sentence contributes value.

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?

Given 6 parameters, no output schema, the description explains the output format (top-N, schemas, examples) and that results are ready to call. Covers all essential aspects for the agent to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. Description adds meaning beyond schema by explaining that query is natural language, lists aliases, and provides examples of how to phrase the query.

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, lists supported domains, and distinguishes itself from siblings by recommending to call it first when many tools are available.

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

Usage Guidelines4/5

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

Explicitly says when to use (browse, search, discover) and advises to call this first when you have many tools. Lacks explicit when-not-to-use but provides strong contextual guidance.

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

All Pkg Go Dev 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

B3.4/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all performing similar data lookups. Additionally, many tools focus on prediction markets and arbitrage, which are unrelated to the server's implied Go development domain, causing confusion.

Naming Consistency2/5

Tool names follow inconsistent conventions: some use snake_case (e.g., 'latest_version', 'list_versions'), some use underscores in longer names (e.g., 'ai_visibility_check', 'ask_pipeworx_grounded'), and some use colons in descriptions but not in names. This mix reduces predictability.

Tool Count2/5

With 35 tools, the count is high for a server named 'Pkg Go Dev' that only offers a few Go module-related tools (e.g., get_go_mod, list_versions). The majority are unrelated Pipeworx tools, making the scope mismatched and excessive.

Completeness1/5

The tool set severely lacks coverage for Go development tasks. It only includes basic module lookup tools (version listing, mod retrieval) but misses essential operations like dependency analysis, build commands, or testing. The vast majority of tools cover unrelated domains (prediction markets, company profiles, etc.), leaving the server incomplete for its intended purpose.

Resources