Skip to main content
Glama
Sign In

Maps Agent

by com.maps-agent
OverviewDiscussionsAdmin

Read a study with its method

get_research
Read-onlyIdempotent

One Maps Agent research or statistics page: the findings with the method behind them (instrument, dataset, sample size, time window, population, exclusions, provenance) and its key figures as data. The structured result carries the whole study in body_markdown. Without a ref: the list of published studies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoA research page URL, path or slug; omit to list the studies.

Output Schema

NameRequiredDescriptionDefault
urlNoThe page on maps-agent.com — cite it.
faqsNoThe page's FAQ, also at the end of body_markdown.
formNoThe page's form.
slugNoIts slug inside the form.
titleNoThe page title.
topicNoGrouping inside the form: answer cluster, guide kind, trade, blog vertical.
totalNoWithout a ref: how many studies are published.
methodNoHow the numbers were measured.
resultsNoWithout a ref: the studies, newest first.
sourcesNoThe sources the page cites; `key` is the footnote marker [^key] in body_markdown.
summaryNoOne or two plain sentences: the page's description or opening.
updatedNoThe page's own last-updated day, YYYY-MM-DD.
key_figuresNoThe study's key figures as published, or null.
method_textNoThe method as a markdown list.
markdown_urlNoThe page's markdown twin.
body_markdownNoThe whole page as markdown: title, URL, date, answer-first opening, body with tables, FAQ and numbered sources. Answer from it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "body_markdown": {
+      "description": "The whole page as markdown: title, URL, date, answer-first opening, body with tables, FAQ and numbered sources. Answer from it.",
+      "type": "string"
+    },
+    "faqs": {
+      "description": "The page's FAQ, also at the end of body_markdown.",
+      "items": {
+        "properties": {
+          "answer": {
+            "type": "string"
+          },
+          "question": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "question",
+          "answer"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "form": {
+      "description": "The page's form.",
+      "enum": [
+        "answer",
+        "guide",
+        "research",
+        "glossary",
+        "blog",
+        "industry",
+        "comparison",
+        "changelog",
+        "page"
+      ],
+      "type": "string"
+    },
+    "key_figures": {
+      "description": "The study's key figures as published, or null."
+    },
+    "markdown_url": {
+      "description": "The page's markdown twin.",
+      "type": "string"
+    },
+    "method": {
+      "description": "How the numbers were measured.",
+      "properties": {
+        "dataset": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "excludes": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "instrument": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "population": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "provenance": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "sample_size": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "window_from": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "window_to": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "method_text": {
+      "description": "The method as a markdown list.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "description": "Without a ref: the studies, newest first.",
+      "items": {
+        "properties": {
+          "form": {
+            "description": "The page's form.",
+            "enum": [
+              "answer",
+              "guide",
+              "research",
+              "glossary",
+              "blog",
+              "industry",
+              "comparison",
+              "changelog",
+              "page"
+            ],
+            "type": "string"
+          },
+          "slug": {
+            "description": "Its slug inside the form.",
+            "type": "string"
+          },
+          "summary": {
+            "description": "One or two plain sentences: the page's description or opening.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "The page title.",
+            "type": "string"
+          },
+          "topic": {
+            "description": "Grouping inside the form: answer cluster, guide kind, trade, blog vertical.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "updated": {
+            "description": "The page's own last-updated day, YYYY-MM-DD.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "The page on maps-agent.com — cite it.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "form",
+          "slug",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "description": "Its slug inside the form.",
+      "type": "string"
+    },
+    "sources": {
+      "description": "The sources the page cites; `key` is the footnote marker [^key] in body_markdown.",
+      "items": {
+        "properties": {
+          "key": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "description": "One or two plain sentences: the page's description or opening.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "The page title.",
+      "type": "string"
+    },
+    "topic": {
+      "description": "Grouping inside the form: answer cluster, guide kind, trade, blog vertical.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "description": "Without a ref: how many studies are published.",
+      "type": "integer"
+    },
+    "updated": {
+      "description": "The page's own last-updated day, YYYY-MM-DD.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "The page on maps-agent.com — cite it.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description adds the dual-mode behavior (single study vs. list of published studies) and points at body_markdown as the carrier of the full study, which is modest but real added context. It says nothing about what happens with an invalid or stale ref, or about list-mode paging.

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 main capability is front-loaded in the first sentence, with the fallback mode trailing. The parenthetical enumeration of method fields is dense but each item is informative. Minor redundancy appears where the no-ref behavior repeats the parameter description.

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?

For a single optional-parameter read tool with full annotations and an output schema, the description covers what is returned (findings, method metadata, figures, body_markdown) and the two operating modes. Edge cases such as an unresolvable ref or list-mode pagination are left unaddressed, but nothing critical for correct invocation is missing.

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 coverage is 100% and the single ref parameter is already documented as 'A research page URL, path or slug; omit to list the studies.' The description's 'Without a ref: the list of published studies' restates that omission behavior rather than adding format or validation meaning. Baseline 3 applies since the schema does the heavy lifting.

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 names a specific resource ('One Maps Agent research or statistics page') and scopes its content precisely: findings plus the method behind them (instrument, dataset, sample size, time window, population, exclusions, provenance) and key figures as data. An agent knows exactly what it gets. It stops short of differentiating itself from get_article or search_knowledge, which is why it isn't a 5.

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

Usage Guidelines3/5

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

The only conditional guidance is the no-ref mode: 'Without a ref: the list of published studies.' That establishes two calling modes but never says when to choose this tool over get_article or search_knowledge, nor any prerequisite for a valid ref. Usage is implied by the description rather than stated as guidance.

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

All Maps Agent toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources