Skip to main content
Glama

Save the team profile

set_team_profile

Save the team profile (admin only). Pass only fields your person approved: spoken_name, pronunciation, about, website, trademarks [{name, say_as}], tone, opening, closing, say [], never_say [], customs (house rules, prose), knock_line ({name} = crew member's first name, {team} = company), caller_name (≤15 chars). It shapes how the crew sounds; it cannot change the rules (the crew says it's an AI when asked, keeps to calling hours, honours do-not-call, invents nothing).

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": {
      "profile": "<profile>"
    },
    "name": "set_team_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesFields to set. Null clears a field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false and openWorld=false, and the description goes beyond them by stating the admin requirement and, importantly, the invariants the save cannot touch (AI disclosure, calling hours, do-not-call, no invention). It does not say whether the save replaces the whole profile or merges into it, which is the main behavioral unknown left.

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?

The permission and the field list are front-loaded and no sentence is filler, but the second half is a long run-on that stacks field names, placeholder syntax and invariants without visual separation. Splitting the invariant clause out would cost nothing and read faster.

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 one-parameter, nested-object mutation with no output schema, the description covers fields, per-field constraints and the rules that cannot be overridden. It leaves open the merge-vs-replace semantics and the response shape, the only real gaps for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema is a single opaque "profile" object, so the description carries the entire field contract: spoken_name, pronunciation, about, website, trademarks [{name, say_as}], tone, opening, closing, say/never_say arrays, customs prose, knock_line placeholders and the ≤15-char caller_name limit. This is meaning the schema does not supply.

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 ("Save the team profile") and immediately qualifies scope with "(admin only)". It is unmistakably the write counterpart to get_team_profile and draft_team_profile among the siblings, so an agent can pick it without opening the schema.

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?

"Pass only fields your person approved" gives a real precondition for calling, and "admin only" rules out non-admin callers. What is missing is an explicit pointer to the sibling that produces the payload (draft_team_profile) or a statement of when not to call.

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.