Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_canned_service

Retrieve detailed information about a specific service template using its ID to access predefined service configurations for automotive repair shops.

Instructions

Get detailed information about a single canned service template by its ID.

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": {
      "id": "<id>"
    },
    "name": "get_canned_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe canned service ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must carry full behavioral disclosure burden. Fails to disclose: read-only nature (implied but not explicit), error behavior for invalid IDs, rate limits, or what 'detailed information' encompasses. Provides minimal safety/operational context beyond the action verb.

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?

Single sentence, front-loaded with no redundant words. Every element earns its place: verb, resource, scope qualifier, and key parameter reference. Appropriately compact for a simple getter.

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?

Adequate for a single-parameter tool with complete schema coverage, but gaps remain given no output schema exists. Description does not hint at return value structure, payload size, or what fields constitute 'detailed information'. Sufficient but minimal.

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%, establishing baseline 3. Description references 'by its ID' which aligns with the parameter, but adds no additional semantic context such as ID format constraints, where to obtain valid IDs, or validation rules beyond the schema's basic 'The canned service ID'.

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?

Clear verb ('Get'), specific resource ('canned service template'), and scope ('single' + 'by its ID'). Distinguishes implicitly from sibling 'list_canned_services' by emphasizing the singular lookup pattern, though it does not explicitly name the alternative.

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?

No explicit guidance on when to use this tool versus alternatives. While 'by its ID' implies you must have a specific identifier, it does not state when to use this versus 'list_canned_services' for browsing, nor does it mention prerequisites like ID discovery.

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