Skip to main content
Glama

Read the consulting overview

get_consulting_overview
Read-only

Read how Rich Steinmetz helps medium and large businesses connect APIs, put AI to work, and improve business software. Use this to check whether the consulting is a fit, see examples of past work, or find links to Rich’s profile and projects.

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

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, so the safety and locality profile is covered without the description. The description adds that the payload is marketing/profile content containing fit information, work examples, and links, which helps an agent anticipate the nature of what it retrieves. It says nothing about size, pagination, or freshness, so the incremental value beyond annotations is modest.

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?

Two sentences, front-loaded with what the tool returns and followed by when to reach for it. Every clause carries information, though the product-marketing framing ('put AI to work') is slightly padded relative to a purely functional statement.

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 an output schema present, return structure needn't be described, and a zero-parameter read-only tool has little else to disclose. The description covers what content is inside and why to call it, which is sufficient. Only the absence of any hint about content volume or relation to the sibling tools leaves a minor gap.

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 baseline of 4 applies. No parameter claims in the description risk conflicting with the empty schema.

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 names a specific resource and verb: it reads a consulting overview describing how Rich Steinmetz helps medium and large businesses with APIs, AI, and business software. That is concrete enough for an agent to know what content comes back. It does not differentiate itself from the siblings (get_solution_definition_call, read_public_page), which keeps it out of 5 territory.

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?

It gives explicit use cases: check fit, see past-work examples, or find links to Rich's profile and projects. That is clear positive guidance. There are no when-not conditions and no mention of an alternative tool to prefer in other situations, so it stops short of a 5.

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