Skip to main content
Glama

Schütze Capital

About Schütze Capital

get_company
Read-onlyIdempotent

Who Schütze Capital is, key facts, who it serves, languages, and how to reach it (booking links, inquiry endpoints, privacy).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds useful content scope beyond that: it discloses that the response bundles identity facts, languages, booking links, inquiry endpoints, and privacy information, which tells the agent what payload to expect. It stops short of describing structure or currency of the facts.

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 a compact parenthetical enumerating the returned content. Every clause carries information and nothing is padded.

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 zero-parameter, non-destructive read with no output schema, the description covers what the agent needs to decide and call. The only minor gap is that it does not hint at the shape or ordering of the returned facts, which matters little for a simple profile lookup.

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 no parameters, so the baseline of 4 applies; there is no argument semantics to document. The description adds no parameter-related noise, which is appropriate 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?

The description names the resource precisely (Schütze Capital's identity, key facts, audience, languages, contact channels) and reads as the canonical 'about' tool. It is distinguishable from siblings like get_faq, get_pricing, and get_services by content scope, though it never names them explicitly.

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?

Usage is implied by the content list: an agent can infer this is the right call for company background and contact routing. There is no explicit when-to-use or when-not-to-use guidance, and no mention that get_faq/get_pricing cover the topical details this tool only summarizes.

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