Skip to main content
Glama

Read the team profile

get_team_profile
Read-only

The team profile the crew works from: company name as spoken, what the team sells, trademarks and how to say them, tone, how calls open and close, words to use and never use, house rules, the knock line, caller-ID name, and per-campaign overrides. Read it first; if is_set is false, offer to build it with draft_team_profile.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by enumerating the shape of the returned data (tone, house rules, knock line, caller-ID, per-campaign overrides) and by disclosing the is_set flag and its branching consequence — a real behavioral detail not present in annotations or any output schema. It stops short of describing response structure or failure modes, which keeps it from a 5.

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?

Two sentences, front-loaded with the core purpose before the inventory and ending on the actionable conditional. The long mid-sentence enumeration is dense but each item signals real profile content an agent may need to reason about, so little is wasted — though the list could be tightened without loss.

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?

With no parameters, no output schema, and only advisory annotations, the description carries the burden of explaining what comes back — and it largely does, listing the profile's contents and calling out the is_set field that drives the next-step decision. Minor incompleteness remains around the exact return shape (nesting of per-campaign overrides, whether missing fields are null or absent).

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not need to compensate for any schema gap here.

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 opening noun phrase 'The team profile the crew works from' plus the enumerated contents make it unambiguous that this returns the team's profile data, and 'draft_team_profile' and the sibling set_team_profile make the read-only variant clear. The only gap is that the verb is implied ('Read it first') rather than stated outright, so the first clause alone reads as a description of a resource rather than an action.

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?

'Read it first' gives explicit ordering guidance, and 'if is_set is false, offer to build it with draft_team_profile' names the exact alternative tool and the condition that selects it. An agent knows both when to call this and what to do as a follow-up, with no inference required.

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.