Conciergr

The team's name and note for a contact

set_contact_name_and_note

Destructive

The team's own name for a contact and a private note (up to 200 and 2,000 characters). The assistant never sees them. An empty value clears it.

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

Input Schema

Name	Required	Description
`name`	No
`note`	No
`brand`	No	Which assistant (its slug from get_overview `brands[].slug`). Leave out when the business has one.
`contact`	Yes	The chat's contact key, from list_chats, list_needs_you or search_chats (`contact`).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already mark the tool as non-readonly and destructive, and the description adds important behavioral context: the name and note are private to the team, the assistant never sees them, and an empty value clears them. It still does not cover permission requirements or how omitted fields behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences with limits and clearing behavior front-loaded. Every clause carries useful information and there is no wasted text.

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?

For a four-parameter mutation tool, the description explains the private fields and clearing semantics but omits explicit usage routing and whether omitting one field preserves or clears the other. No output schema is present, but that does not create an additional gap here.

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 50%, with contact and brand documented in the schema. The description meaningfully covers the two undocumented parameters by giving character limits for name and note and explaining that empty values clear them, though it does not clarify omitted-versus-null behavior.

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 clearly identifies the resource and fields: the team's private name and note for a contact, with character limits. It does not differentiate this tool from sibling settings/contact tools, so it is clear but not fully disambiguated.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use or when-not-to-use guidance, nor does it name alternatives such as update_settings. Usage is only implied by the private-name/note context.

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

All Conciergr tools Inspect

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

Need Help?