Skip to main content
Glama

get_shop

A local shop that takes visit requests through the Fifty Asks booking widget (its id is in the shop's booking link, fiftyasks.com/b/): name, area, phone, services, and the fields a request needs.

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": {
      "shop_id": "<shop_id>"
    },
    "name": "get_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
shop_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and largely drops it. It never states that this is a read-only lookup, what happens for an unknown or malformed id, or whether results are cached or rate-limited; the only behavioral hint is an implicit list of returned fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single sentence with no padding, but it is front-loaded with a resource definition instead of the verb and action, and the embedded parenthetical about the booking widget interrupts the flow. Restructuring to lead with the operation would earn more.

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?

For a one-parameter getter with no output schema, listing the returned fields (name, area, phone, services, request fields) does much of the work a return-value section would. However, the missing action statement and any failure behavior leave it short of complete.

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 0% and shop_id is undocumented in the schema, but the description compensates well by explaining that the id lives in the shop's booking link and showing its format (fiftyasks.com/b/<id>). That is genuinely actionable information an agent could not derive from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The description identifies the resource (a local shop) and enumerates the data it carries — name, area, phone, services, request fields — but never states the action. It reads as a noun-phrase definition of a shop rather than 'retrieves a shop's profile,' and it does nothing to distinguish itself from siblings like get_visit_request or get_booking.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The mention of the booking link explains where the id comes from, which is parameter help, not routing advice; an agent gets no signal for choosing get_shop over get_visit_request or get_booking.

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.

Resources