Skip to main content
Glama

Read Solution Definition Call details

get_solution_definition_call
Read-only

Read the published price, payment terms, and Google Calendar link for Rich’s Solution Definition Call. Use this when someone asks what the call covers, how much it costs, when they would pay, or how to pick a time. The link opens the booking page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
uriYesCanonical URL of the Markdown document.
pageYesShort name of the public page.
markdownYesFull text of the Markdown document.
mimeTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, and the description correctly aligns with that read-only framing. It adds modest context beyond the annotations: the data is 'published' and the returned link resolves to a live booking page. It says nothing about freshness, auth, or whether the price can change, so it is useful but not rich.

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?

Three short sentences, front-loaded with what is returned, then when to use it. The closing line 'The link opens the booking page' adds only marginal value on top of the preceding sentence about the calendar link.

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?

For a parameterless read with annotations and an output schema, the description covers both content and invocation triggers, leaving little an agent needs in order to call it correctly. The one small gap is that it does not say whether the returned details are static or periodically updated.

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 nothing for the description to disambiguate and the input schema is trivially complete. Baseline 4 applies; no parameter-level elaboration is needed or expected here.

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 ('Read') plus a named resource and an enumeration of the fields returned (published price, payment terms, Google Calendar link) for a well-identified item. It does not name sibling tools such as get_consulting_overview or read_public_page, so the differentiation is by content rather than by explicit contrast.

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

Usage Guidelines4/5

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

Gives four concrete trigger questions that map directly to the returned fields ('what the call covers, how much it costs, when they would pay, how to pick a time'), which is strong when-to-use guidance. It stops short of stating exclusions or pointing to an alternative tool for adjacent questions.

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