Skip to main content
Glama

Schütze Capital

Schütze Capital services

get_services
Read-onlyIdempotent

The services Schütze Capital offers, who each is for, its page, and its published price or how pricing works.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety behavior is fully covered without help from the description. The description adds return-content context by saying pricing may be a published figure or an explanation of how pricing works, which is useful but modest. It says nothing about size limits, pagination, or completeness of the list, so it stays at baseline-plus.

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?

It is a single compact phrase with no filler, and the most important information (services offered) comes first. The fragment 'its page' is slightly ambiguous, and the sentence lacks a verb, but nothing is wasted.

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 lookup with no output schema, the description is complete enough: it tells the agent the shape of the returned data (service, audience, page, pricing). The one gap is that it never states whether it is a full catalog or a summary, which leaves overlap with get_pricing unresolved.

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 and the baseline is 4. The description neither adds nor omits anything relevant 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 tells you the resource (Schütze Capital's services) and enumerates the specific fields returned: audience ('who each is for'), page, and pricing. It is clearer than the bare name, but it never names a verb and never distinguishes this catalog from the sibling get_pricing, which covers overlapping ground.

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?

There is no when-to-use statement, no prerequisites, and no mention of alternatives such as get_pricing or get_faq. The agent has to infer usage from the name alone, and nothing tells it whether to call this or the dedicated pricing tool first.

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