Skip to main content
Glama

How sponsoring works

get_sponsor_info
Read-only

Use this when an adult asks how a local business or community group can appear on 2hives, or what the sponsor packages are. Not for medical questions, emergencies or a crisis. Not for general chat about meditation. Not for personal listening.

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

Input Schema

NameRequiredDescriptionDefault
countryNoOptional ISO country code of the business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered without the description. The description adds topical scope but says nothing about the shape of the answer, whether package details are static or region-dependent, or any caveats about pricing accuracy. Useful routing context, but no behavioral depth beyond the annotations.

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 front-loaded with the activation condition and kept to four short sentences. The negative sentences are individually terse, though the run of three consecutive 'Not for...' lines is slightly listy without being verbose.

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 simple read-only info tool with one optional parameter and no output schema, the description covers who should trigger it and what topic it answers. The remaining gap is whether the country argument changes the answer and what the caller receives (contact form, link, package text), which an agent would want to know before acting on the result.

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?

The single optional 'country' parameter is fully documented in the schema (100% coverage) with an ISO-code example. The description never mentions country filtering or whether packages differ by region, so it adds no meaning beyond the schema; baseline 3 applies.

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 ('how a local business or community group can appear on 2hives', 'sponsor packages'), so an agent knows this is a sponsorship/packages information tool rather than a meditation-content tool. It lacks an explicit verb like 'returns' or 'explains', and it never contrasts itself with a named sibling, leaving differentiation to topical exclusions.

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 a clear activation condition ('when an adult asks how a local business or community group can appear... or what the sponsor packages are') and four explicit exclusion domains (medical, emergencies/crisis, general chat, personal listening). It stops short of naming which sibling to route those excluded intents to, so the agent must still infer the alternative.

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