Skip to main content
Glama

get_business_profile

Read-only

Retrieve business profile details—name, currency, tax rate, and terms—to keep quotes and invoices accurate.

Instructions

Show the business profile used on quotes and invoices (name, currency, tax rate, terms).

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

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds that the profile is the one appearing on quotes and invoices, which gives useful domain context, but it says nothing about permissions, defaults if unset, or behavior of the returned terms/currency values.

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?

A single front-loaded sentence with the resource named first and the field enumeration compact. Zero filler and nothing an agent must skip over.

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?

A zero-argument read tool with an output schema and read-only annotations is nearly self-describing, and the description covers the only open question — what the profile contains. It stops short of noting whether fields can be empty or how the profile relates to document generation beyond a passing mention.

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, so there is no parameter semantics to explain; baseline is 4. The description correctly does not invent parameters and its field list instead describes payload content, which is harmless context.

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?

Specific verb ('Show') plus resource ('business profile') with a parenthetical enumerating the fields returned (name, currency, tax rate, terms), so the agent knows exactly what this retrieves. It does not explicitly name the sibling update_business_profile as the mutation counterpart, but the read/mutate pairing is inferable from the name.

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?

The phrase 'used on quotes and invoices' implies the context in which this profile matters, but there is no explicit when-to-use, when-not-to-use, or routing to update_business_profile. For a simple no-argument read, that implied framing is adequate but not instructive.

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