Skip to main content
Glama

Pumpkin

service_windows

Read-only

Find provisional service windows. Staff must confirm.

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": {
      "site": "<site>",
      "itemId": "<itemId>"
    },
    "name": "service_windows"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
itemIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds a useful behavioral caveat that results are 'provisional' and require staff confirmation, but it does not explain how confirmation should occur or what the results represent.

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 definition is two short sentences with the purpose front-loaded and no wasted wording. It is very terse, but that terseness reflects missing detail rather than verbosity or poor structure.

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

Completeness2/5

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

For a two-parameter lookup tool with no output schema, the description is too sparse: it does not explain what a service window is, what itemId identifies, or how these results relate to service_estimate or service_request_submit. Annotations cover safety, but key invocation context remains missing.

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

Parameters2/5

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

The schema documents the 'site' parameter as the site ID returned by find_business, but 'itemId' has no schema description. The tool description adds no parameter meaning at all, leaving the required itemId undefined in both the schema and the prose.

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 states a clear verb and resource: 'Find provisional service windows.' It is not a tautology and gives the agent a usable sense of the operation. However, it does not explicitly differentiate this lookup from siblings such as service_search, service_estimate, or check_service_area.

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?

The only workflow hint is 'Staff must confirm,' which describes a confirmation requirement rather than when to choose this tool over alternatives. It does not state when to use it, what prerequisite checks are needed, or which sibling to use for related tasks.

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