Skip to main content
Glama

Promise Land Appraisal public information

Get business profile

get_business_profile
Read-onlyIdempotent

Read the business identity, public contact details, and Greater Houston service area.

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
businessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already cover safety and idempotency: readOnly, idempotent, destructive=false, openWorld=false. The description adds useful scope beyond that: it identifies the data returned and the Houston-specific geographic limit on the service area, which a caller would otherwise not know. It does not discuss permissions, but for a read-only profile tool with no parameters, that is a minor gap.

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?

It is a single sentence with no wasted words. The content is front-loaded with the verb and then expands to the concrete data covered. Its length fits the simplicity of a zero-argument read tool.

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?

The tool has no parameters, an output schema that documents return values, and annotations that specify the safety profile. The description fills in the content scope that the schema and annotations cannot express. Only the relationship to the sibling tools that also expose service-area data is left unaddressed.

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 input schema has zero parameters, so the baseline is 4. The description does not add parameter meaning, but none is needed because there is nothing to describe.

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 uses a specific verb, 'Read', and then names three concrete resources: business identity, public contact details, and the Greater Houston service area. This is clearer than a bare restatement of the name. However, it never distinguishes this tool from the sibling list_service_areas, which also concerns service-area data.

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 description never states when to use this tool instead of the alternatives, such as list_service_areas or get_request_information, and it offers no exclusions. The zero-parameter read-only nature implies it is for a static profile lookup, but that implication is left entirely to the agent.

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