Skip to main content
Glama
mcp-starter-kit

mcp-starter-kit

by 0xJRP

Get business info

get_business_info

Retrieve a business's name, contact details, address, and opening hours to answer questions about the business itself.

Instructions

Returns the business name, contact details, address, and opening hours. Use this to answer questions about the business itself.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_business_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. "Returns" signals a read-only, side-effect-free operation and the field enumeration doubles as return-value documentation since there is no output schema, but nothing is said about freshness, auth requirements, or whether the data is static configuration.

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?

Two sentences, zero filler, and the payload (what fields come back) is front-loaded ahead of the usage hint. Every clause earns its place.

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

Completeness4/5

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

With no output schema, the description is the only place that tells the agent what is returned, and it does so by listing the four field groups. For a zero-param, low-risk lookup that is essentially sufficient, though it omits any note on data staleness or fallback behavior when details are unavailable.

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?

The tool takes zero parameters and the description correctly presents it as a no-input lookup, so there is nothing misdescribed. Baseline 4 applies for a parameterless tool; it gains nothing extra but loses nothing.

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?

"Returns the business name, contact details, address, and opening hours" gives a specific verb plus an enumerated resource, so the agent knows exactly what data this yields. It does not explicitly differentiate itself from lookup_faq, which is the nearest sibling by topic, so it falls short of a 5.

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

Usage Guidelines3/5

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

"Use this to answer questions about the business itself" implies the usage context (identity/contact/logistics questions) but gives no explicit exclusion. An agent must infer on its own that hours questions go here rather than to check_availability, and FAQ-style questions go to lookup_faq.

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