Storefinch

Get details for several businesses

get_places

Read-onlyIdempotent

Fetch complete records for up to 25 places in one call: the same fields as get_place (every email and social profile, coordinates, category path, operating status, sources and license, a Google Maps link, and any verify_websites or find_emails results). Use it to compare or review a shortlist from search_places; for more than 25 places use export_leads. Ids not in the current release are listed in not_found instead of failing the call. Each id found counts as one call.

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": {
      "place_ids": "<place_ids>"
    },
    "name": "get_places"
  }
}

Input Schema

Name	Required	Description	Default
`place_ids`	Yes	Up to 25 place ids from search_places, export_leads or get_place, e.g. ["08f2a..."].

Output Schema

Name	Required	Description
`places`	Yes	Full records for the ids found, in the order given.
`not_found`	No	Ids not in the current release (ids can change monthly; search again).
`data_release`	Yes
`quota_remaining`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed world), yet the description adds non-obvious behavior: unknown ids are returned in not_found rather than failing the whole call, and cost is per id found ('Each id found counts as one call'). Partial-failure and billing semantics are exactly the context annotations cannot express.

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?

Front-loaded with the operation and its cap, then usage, then edge cases and cost — a sound ordering. The parenthetical field enumeration is somewhat long and partly duplicates the existing output schema, keeping it from a 5.

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?

An output schema exists, so return values needn't be detailed; the description still covers the batch cap, the partial-failure path, cost accounting, and the sibling alternative. Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining what happens to id values that are not in the current release (routed to not_found instead of erroring). It adds outcome semantics for the parameter rather than just restating its type.

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?

States a specific verb and resource with scope: 'Fetch complete records for up to 25 places in one call'. It also anchors the shape of the result ('the same fields as get_place'), which lets an agent distinguish it from get_place (single) and export_leads (bulk) without opening any schema.

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?

Names the concrete scenario ('compare or review a shortlist from search_places') and the exclusion with its alternative ('for more than 25 places use export_leads'). Both the when and the when-not are explicit, leaving nothing to inference.

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

All Storefinch tools Inspect

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

Need Help?