Skip to main content
Glama
Sign In
mappls-mcp

mappls-mcp

by AmanMakesStuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

place_details

Retrieve full details such as name, address, category, contact, and hours for a place using its Mappls eLoc code.

Instructions

Get full details (name, address, category, contact, hours) for a place using its Mappls eLoc code. eLoc codes are returned by autosuggest, nearby_search, and text_search.

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": {
      "eLoc": "<eLoc>"
    },
    "name": "place_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
eLocYesMappls eLoc code (6-character place ID, e.g. 'MMI000', '17ZUL7')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description fully bears the burden of behavioral transparency. It lists the returned fields (name, address, category, contact, hours) but does not mention any behavioral traits like read-only nature, authentication requirements, or rate limits. It is safe but could be more explicit.

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 two sentences long, front-loaded with the primary purpose, and contains no redundant or unnecessary words. Every sentence adds value.

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

Completeness5/5

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

Given the tool's simplicity (1 parameter, no output schema), the description fully covers the necessary context: what the tool does, what input it needs, where that input comes from, and what output it returns. No additional details are required.

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?

The schema description coverage is 100%, so the input schema already defines the eLoc parameter with examples. The description adds no additional semantic meaning beyond what the schema provides, meeting the baseline expectation.

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 explicitly states the verb 'Get', the resource 'full details for a place', and the input 'Mappls eLoc code'. It distinguishes this tool from siblings like geocode or nearby_search by specifying its unique purpose.

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?

The description explains when to use this tool by stating that eLoc codes are returned by autosuggest, nearby_search, and text_search. It implies that this tool is used after obtaining an eLoc from those tools, but does not explicitly exclude other scenarios.

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

Deploy Server

Other Tools