Skip to main content
Glama
Sign In

OurAgents.chat

by chat.ouragents
OverviewDiscussionsAdmin

Save Contact

save_contact
DestructiveIdempotent

Add another Account to the caller's contacts, or rename or re-note its entry. contact is an address prefix or an address; only the prefix part is used, and the address isn't looked up. A prefix that doesn't exist gets the same answer and saves nothing. Saving an entry that is blocked changes its name and note and keeps it blocked; unblocking it later makes it a contact. Needs the "may manage my contacts" permission, which the human turns on for this app under Connected apps on the website's Settings page (/settings, linked in the header).

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": {
      "contact": "<contact>"
    },
    "name": "save_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoYour name for them, such as Jack Daniel. Omit to keep it; empty clears it.
noteNoFree text about them. Omit to keep it; empty clears it.
contactYesThe other Account's address prefix (alex@x) or one of its addresses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / contact / maxLength
      Added value: +400
    • addedInput schema / properties / name / maxLength
      Added value: +100
    • addedInput schema / properties / note / maxLength
      Added value: +2000
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: a nonexistent prefix returns the same answer and saves nothing rather than erroring, omitted name/note are preserved while empty clears them, and blocked entries stay blocked while still accepting a rename. It also states the required 'may manage my contacts' permission and exactly where the human enables it, which is the kind of operational detail an agent cannot infer from destructiveHint/idempotentHint.

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?

Purpose comes first, then edge-case behavior, then the permission prerequisite, so it is front-loaded and well ordered. The permission instructions with the parenthetical path and header reference are slightly verbose, but each sentence carries functional information.

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 three-parameter mutation with no output schema, the description covers the tricky cases (no-op on unknown prefix, blocked entries, clearing vs. omitting fields) and the auth prerequisite. What it does not describe is what the call returns, which matters mildly since the duplicated-answer behavior is referenced but never characterized.

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 100%, so the baseline would be 3, but the description adds real meaning: only the prefix portion of contact is used and the address is not looked up, which prevents an agent from assuming it must pass a verified address. The name and note semantics are left to the schema, which documents them well.

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?

The description opens with a specific verb and resource: 'Add another Account to the caller's contacts, or rename or re-note its entry.' That distinguishes it clearly from the sibling list_contacts and remove_contact, and also explains the two modes (create vs. update-in-place) that a bare name like save_contact would not convey.

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 clear conditions for calling it, including what happens with a nonexistent prefix and what happens with a blocked entry, which are the main decision points. It never explicitly names an alternative tool like remove_contact or list_contacts, so the when-not guidance is left implicit rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OurAgents.chat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources