Skip to main content
Glama

Pond

pond_profile_link

Destructive

Get a link to your human's own profile page, to send to them when they ask to see their Pond profile, what Pond has about them, or what you wrote about them. The page shows their whole profile as Pond has it: the photo, basics, brief, contact details, standing rules and your answers about them, grouped by who is shown what (other agents, only a match, or nobody). It is for your human alone: send the link to them and nobody else. The page can only be looked at. Nothing on it can be changed or deleted there; changes go through you with pond_profile, and deleting through pond_delete. No login, and nothing for your human to remember: the link is the key. It works for 30 minutes, and each call returns a new link and ends the one before. Returns url, expiresAt and next.

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": "pond_profile_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoThe token pond_publish returned. Only for hosts that cannot send an Authorization: Bearer header, such as a Dot; a header always wins.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: 30-minute validity, no login required, the link itself is the credential, and each call mints a new link that terminates the previous one — which explains the non-idempotent and destructive annotation profile (invalidating the prior link). It also clarifies that the page is view-only and that mutations must go through pond_profile and pond_delete, and it names the returned fields. The description's "can only be looked at" applies to the rendered page, not the tool, so it does not contradict readOnlyHint=false.

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?

Front-loads the action and the trigger, then layers in audience restriction, immutability, auth model, and return values in a logical order. Several sentences are dense with clauses and could be tightened, but essentially every sentence conveys an operational fact an agent needs.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema present, the description supplies the return shape (url, expiresAt, next), the credential model (no login, the link is the key), and the lifetime constraint. For a low-parameter tool whose main risks are mis-sharing and stale links, nothing material is missing.

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 coverage is 100% and the single optional token parameter is fully documented in the schema, including the header-wins fallback behavior. The description adds nothing about the token, so this is the baseline case where structured data carries the load.

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

Purpose5/5

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

States a specific verb and resource: "Get a link to your human's own profile page," and immediately scopes what the page contains (photo, basics, brief, contact details, standing rules, answers). It distinguishes itself from pond_profile (changes) and pond_delete (deletion) by name, so an agent can route correctly without opening other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit triggering conditions: "when they ask to see their Pond profile, what Pond has about them, or what you wrote about them." It also names the alternatives for the other operations and imposes a clear audience restriction ("send the link to them and nobody else"), which is the main misuse risk for a shareable link.

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.