Skip to main content
Glama

Schütze Capital

Ask Schütze Capital for a quote

request_quote
Idempotent

Send Schütze Capital a quote request on behalf of a person. Returns an automated acknowledgement and the booking link. Set consent to true only if the person agreed to be contacted. A person on the team answers; nothing is emailed automatically.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "need": "<need>",
      "contact": "<contact>",
      "consent": "<consent>",
      "on_behalf_of": "<on_behalf_of>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the person needs, in their words: the problem, scope, roles or volumes.
testNoTrue to test an integration: recorded and marked as a test, nobody follows up.
agentNoThe agent sending this (optional but recommended). The User-Agent header is recorded too.
budgetNoBudget or range, free text (e.g. "$20k-30k a month").
companyNoThe organization the person represents.
consentYesTrue only if the person named in contact agreed to be contacted by this company about this inquiry.
contactYesThe person to answer. An email or a phone is required.
languageNoLanguage for the answer.
timelineNoWhen they want to start or decide.
on_behalf_ofYesWho the agent acts for: the person and, if any, their organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, idempotent open-world write. The description adds real value beyond that: it discloses the return ('automated acknowledgement and the booking link'), that a person on the team answers, and crucially that 'nothing is emailed automatically,' which counters the openWorld write assumption of automated follow-up.

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?

Four compact sentences, front-loaded with the action, with the consent rule and the follow-up behavior surfaced early. There is minor overlap between the title and the first sentence, but nothing is extraneous or wasting space.

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 no output schema, the description correctly fills the gap by describing what the caller gets back (acknowledgement plus booking link) and how follow-up happens. For a 10-parameter nested submission tool, this covers the essentials an agent needs, with the only gap being sibling differentiation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters, and 0-of-enum detail is covered. The description reinforces the consent semantics but largely repeats what the schema's consent field already states, adding only the softer 'agreed to be contacted' phrasing rather than new parameter meaning.

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?

States a specific verb and resource ('Send Schütze Capital a quote request on behalf of a person'), which an agent can readily grasp. It does not, however, explicitly distinguish this from the sibling send_inquiry tool, so the agent may need to infer which submission path is intended for quote requests versus general inquiries.

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 consent instruction ('Set consent to true only if the person agreed to be contacted') gives useful usage gating. But there is no explicit when-to-use guidance versus get_pricing, send_inquiry, or get_faq, so the agent must guess how a quote request differs from a general inquiry or pricing lookup.

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