Skip to main content
Glama

mathjs

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. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable context: it returns top-N tools with 'names, descriptions, and full input schemas (with curated examples)' and states that 'each result is ready to call directly, no second schema lookup needed.' This goes beyond the safe-read trait to describe the response format and eliminates a potential follow-up step, but it doesn't discuss ranking criteria or rate limits.

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?

The description is three sentences, front-loaded with the primary action ('Find tools by describing...'). The second sentence is dense but justified, packing a domain list and return-format details. No filler words; it is efficient for the amount of information conveyed.

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 the tool is a meta-discovery tool with 6 parameters and no output schema, the description adequately explains the return value (tools with schemas ready for direct invocation) and the intended use. It could mention how relevance ranking works or what 'top-N' is based on, but the provided context is sufficient for an agent to invoke it correctly.

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%: all parameters (query, q, task, limit, search, description) have explicit descriptions and aliases, with examples provided in the schema. The description itself does not add parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 opens with 'Find tools by describing the data or task', a specific verb+resource statement. It clarifies the tool's role as a discovery meta-tool and lists concrete domains (SEC filings, FDA drugs, FRED, etc.), which distinguishes it from sibling tools that operate on specific data or perform analysis.

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?

Explicit usage direction is given: 'Use when you need to browse, search, look up, or discover what tools exist' and 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This clearly indicates when to use it over other tools and reinforces its place as an initial discovery step.

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

All mathjs 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.6/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially the ask_pipeworx family (4 variants) and polymarket tools (5 variants). The memory tools (remember/recall/forget) and subscription tools also overlap with each other. While descriptions provide some differentiation, the sheer number of similar tools makes it hard for an agent to quickly distinguish the right one.

Naming Consistency2/5

Most names use snake_case, but there is no consistent verb_noun pattern. Some are verb_noun (ask_pipeworx, resolve_entity), some are noun_noun (bet_research, entity_profile), and others are adjective_noun (recent_changes, pipeworx_trending). The naming is arbitrary and doesn't follow a predictable convention.

Tool Count2/5

At 33 tools, the count is high but not extreme for a broad data platform. However, the server is named 'mathjs', implying a math focus, yet only 2 tools (evaluate, convert_units) are math-related. The vast majority of tools belong to a completely different domain (data lookups, prediction markets, subscriptions), making the count inappropriate for the server's apparent purpose.

Completeness1/5

For a math server, the tool surface is severely incomplete—missing basic operations like plotting, equation solving, calculus, etc. For the actual data integration and prediction market functionality, the set is more complete, but the server name misleads. The mismatch between name and content makes the completeness score very low based on the implied domain.

Resources