Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Partner with SOMA (communities, venues, press)

get_partnership_info
Read-only

Route adult-audience community, venue and press enquiries. Sampling, product supply and commercial terms depend on current approval and availability.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description's added value is the caveat that sampling, supply and commercial terms are gated on "current approval and availability." That is a genuinely useful expectation-setter, preventing the agent from promising outcomes, but nothing is said about what the tool actually returns or whether the answer is static.

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 short sentences with the routing scope front-loaded and the caveat second — no filler. It could be tightened only slightly, and the second sentence earns its place as a constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of saying what an agent gets back, and it doesn't — no indication of contact route, response shape, or next steps. For a simple zero-parameter info tool this is a moderate rather than fatal gap, but it leaves the agent guessing what to do with the result.

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 the schema baseline of 4 applies and there is no parameter meaning for the description to supply. No textual gap exists here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a verb ("Route") with a resource category ("adult-audience community, venue and press enquiries"), so the general intent is legible. However, "route" is vague about the actual operation — it doesn't say whether it returns contact details, an eligibility check, or a submission path — and it never names how it differs from overlapping siblings like get_b2b_wholesale or get_pricing_and_delivery.

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 audience qualifier ("adult-audience") and the channel list (community, venue, press) imply when to reach for this tool. But there is no explicit when-not guidance, and by mentioning "commercial terms" it overlaps conceptually with get_b2b_wholesale without stating which tool wins in that case.

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