Skip to main content
Glama

Pond

pond_profile

Destructive

Change your human's Pond profile when something about them changes or they ask you to: a new photo, city, age range, phone number, brief, or anything else publish took. Pass only what changes; everything you leave out stays. A new brief follows the same rules as at publish: third person, markdown, no names, nothing about their employer, health, finances or other people, and never quotes from their email, messages, calendar or files. Pass a new photo as photoUrl, or as photo if you're an agent hosted by OpenAI and it reaches you as a file. Picks already made stand, and a match sees the new details. With nothing to change, it shows the profile as Pond has it, so check it there before you change anything. Never publish again to change a profile: that makes a second one.

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

Input Schema

NameRequiredDescriptionDefault
ageNoa number between 18 and 99
cityNoa string at most 120 character(s) long
briefNoa string at most 6000 character(s) long
emailNoAn empty string or null clears it.
photoNoThe photo as a file, for an agent hosted by OpenAI, such as a Dot, whose host hands it over this way. Otherwise leave it out and pass photoUrl.
tokenNoThe token pond_publish returned. Only for hosts that cannot send an Authorization: Bearer header, such as a Dot; a header always wins.
genderNo
countryNoISO-3166-1 alpha-2 country code, uppercase, e.g. IS
ageRangeNo
photoUrlNoa string matching the pattern ^(https:\/\/[^\s]+|data:image\/(jpeg|png|webp);base64,[A-Za-z0-9+/]+={0,2})$
radiusKmNoa number between 1 and 500
firstNameNoa string at most 80 character(s) long
availabilityNoa string at most 200 character(s) long
interestedInNo
privateLayerNoOnly what changes in it. phone: E.164, like +3548221234; it can be changed, not removed. instagram and snapchat: the username alone; null removes one. Each is released only on a match.
standingInstructionsNoRules your human set, like "no smokers". An empty string or null clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the risk profile is supplied structurally; the description adds genuine value on top with partial-update semantics ('Pass only what changes; everything you leave out stays'), the consequence that 'Picks already made stand, and a match sees the new details', and the warning that re-publishing creates a duplicate profile. However, the no-argument call described as a read that returns the profile sits somewhat awkwardly against the destructive, non-read-only annotations, and no return shape, error or permission behavior is described.

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-loaded with the action and the field list, then rules, then pitfalls, which is a sensible order for an agent scanning quickly. It is dense but nearly every sentence carries a distinct constraint; the long brief-rules sentence is the one place wording could be tightened without losing meaning.

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?

For a 16-parameter destructive mutation with no output schema, the description covers the pieces an agent actually needs: partial-update contract, field-specific conventions, content policy for the brief, the sibling to avoid, and the no-change read behavior. The absence of return-value documentation is acceptable since the tool returns the profile state and the description says so.

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?

Schema coverage is already 81%, so the baseline is 3; the description earns above that by supplying cross-parameter semantics the schema cannot express — partial update, nothing-left-out persistence, and the photoUrl vs photo routing rule for OpenAI-hosted agents. It also encodes content rules for the brief that are not in the schema. It does not add meaning for many individual fields (age, city, radiusKm, availability, gender, interestedIn, country, standingInstructions), which keeps it below 5.

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 ('Change your human's Pond profile') and enumerates the concrete fields it covers (photo, city, age range, phone, brief). It also names the sibling it must not be confused with — 'Never publish again to change a profile: that makes a second one' — so the boundary with pond_publish is unambiguous.

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 triggers ('when something about them changes or they ask you to'), explicit exclusions (don't use pond_publish to edit), and a documented no-argument behavior that turns the call into a read ('With nothing to change, it shows the profile as Pond has it, so check it there before you change anything'). Little is left to inference about when to reach for this tool.

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.