Skip to main content
Glama

Full Query

full_query
Read-onlyIdempotent

Get the full structured result from Wolfram Alpha. Returns named "pods" (Input, Result, Solution, Plot, Properties, etc.), useful when short_answer is too terse or you need multiple facets (e.g., element properties, equation solution + plot + alternate forms).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "solve x^2 - 5x + 6 = 0"
    },
    "name": "full_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language query
unitsNometric | imperial (default metric)
formatNoplaintext (default) | plaintext,image, plaintext is most agent-friendly.
include_podsNoComma-separated pod IDs to restrict (e.g., "Result,Solution"). Default: return all.

Output Schema

NameRequiredDescriptionDefault
podsNoArray of result pods with structured data
tipsNoUsage tips from Wolfram Alpha
queryYesThe query string that was sent to Wolfram Alpha
messageNoError message if success is false
successYesWhether Wolfram Alpha found a valid interpretation
pod_countNoNumber of result pods returned
did_you_meanNoSuggested alternative interpretations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"plaintext (default) | plaintext,image — plaintext is most agent-friendly."New value: +"plaintext (default) | plaintext,image, plaintext is most agent-friendly."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "query": "solve x^2 - 5x + 6 = 0"
      +  },
      +  {
      +    "include_pods": "Result,Properties",
      +    "query": "properties of gold"
      +  },
      +  {
      +    "format": "plaintext",
      +    "query": "current time in Tokyo"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "did_you_mean": {
      +      "description": "Suggested alternative interpretations",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "message": {
      +      "description": "Error message if success is false",
      +      "type": "string"
      +    },
      +    "pod_count": {
      +      "description": "Number of result pods returned",
      +      "type": "integer"
      +    },
      +    "pods": {
      +      "description": "Array of result pods with structured data",
      +      "items": {
      +        "properties": {
      +          "contents": {
      +            "description": "Plain-text content from all subpods joined by newlines",
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "Pod identifier",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "images": {
      +            "description": "URLs of images in this pod",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "position": {
      +            "description": "Display position of the pod",
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "primary": {
      +            "description": "Whether this is the primary result pod",
      +            "type": "boolean"
      +          },
      +          "title": {
      +            "description": "Pod title (e.g., 'Input', 'Result', 'Solution')",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "id",
      +          "primary",
      +          "position",
      +          "contents",
      +          "images"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "query": {
      +      "description": "The query string that was sent to Wolfram Alpha",
      +      "type": "string"
      +    },
      +    "success": {
      +      "description": "Whether Wolfram Alpha found a valid interpretation",
      +      "type": "boolean"
      +    },
      +    "tips": {
      +      "description": "Usage tips from Wolfram Alpha",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "query",
      +    "success"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description only needs to add context. It adds the shape of the response by naming the pod types, but says nothing about output size, latency, or how pod selection changes cost — the practical behaviors an agent weighing this against short_answer would want.

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?

Two sentences, zero filler, with the purpose front-loaded and the sibling comparison immediately after. Nothing in the text could be removed without losing information.

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 rich annotations and an output schema, the description needs only to explain intent and the richer-output tradeoff, both of which it does. The remaining gap is operational: no mention of response size or latency, which matters for a tool that returns full pod sets instead of a terse answer.

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%, so every parameter (query, units, format, include_pods) is already documented, which sets the baseline at 3. The description's examples of multi-facet queries hint at how include_pods is used in practice, but add no syntax or format details beyond the schema.

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 uses a specific verb and resource ("Get the full structured result from Wolfram Alpha") and then says exactly what comes back (named pods such as Input, Result, Solution, Plot, Properties). It explicitly distinguishes itself from the short_answer sibling, so an agent can pick between them without opening either schema.

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?

It states the selecting condition clearly: use this when short_answer is too terse or when multiple facets are needed, and gives concrete examples (element properties, equation solution plus plot). It stops short of saying when not to use it, or noting the tradeoff of a larger, slower response that might favor short_answer for simple lookups.

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.