Skip to main content
Glama
TomTom MCP Server

TomTom MCP Server

Official

Get App Data

tomtom-get-app-data
Read-onlyIdempotent

Fetches missing app data for data-visualization results by rerunning the data-viz tool when inline data is absent or fails to decode.

Instructions

Internal tool for the data-viz app to get data missing from the result, by running tomtom-data-viz again

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool": "<tool>",
      "arguments": "<arguments>",
      "reason": "<reason>"
    },
    "name": "tomtom-get-app-data"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe tool whose result the app draws, from the result's _meta.tool
reasonYesWhy the app fetches: the result had no inline app data, or it failed to decode
argumentsYesThat tool call's arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.14
    • changedInput schema / properties / tool / description
      Previous value: -"The tool whose result the app draws, from the text's _meta.tool"New value: +"The tool whose result the app draws, from the result's _meta.tool"
  2. Addedv1.6.13

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool reruns tomtom-data-viz, which is useful behavioral context, but it does not discuss return behavior, permissions, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single tight sentence with no filler. Each clause contributes useful context: internal scope, target app, missing-data purpose, and rerun mechanism.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The annotations and schema cover safety and parameters well, but with no output schema the description does not explain what data is returned or how the rerun result is shaped. It is adequate but leaves return-value context implicit.

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 the schema already documents all three parameters, including the reason enum and the nested arguments object. The description adds no parameter-level detail beyond the schema, 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific operation: getting data missing from a result by rerunning tomtom-data-viz. It distinguishes this internal retrieval path from the broader tomtom-data-viz sibling, though the phrase “get data missing” remains somewhat internal-app-specific.

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 gives clear usage context: this is an internal tool for the data-viz app and is used when data is missing from a result. It does not spell out when-not conditions or alternatives, but the context is sufficiently clear.

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