Skip to main content
Glama

Team: profile completion and next question

team_profile_status
Read-onlyIdempotent

How complete your Our Team page is: percent with a transparent per-field rubric, what is missing, what you skipped, the public page URL, and the single next question to ask (field, prompt, why, example; each optional). Does not change anything.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for the question texts (fa or en; default: your account language).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Does not change anything' is largely redundant. What the description adds beyond the structured fields is the return profile: a percent score backed by a transparent per-field rubric, missing vs. skipped items, a public page URL, and a single next question decomposed into field, prompt, why, and example, with those parts marked optional. With no output schema present, that disclosure of response contents is the main source of value.

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?

It is a single dense sentence that front-loads the core deliverable (completion percent) and then enumerates the accompanying outputs, ending with the behavioral reassurance. The parenthetical '(field, prompt, why, example; each optional)' is compact and earns its space by defining the question object. No filler sentences.

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 simple, zero-required-parameter read tool with no output schema, the description covers what an agent needs: the meaning of the percent, the rubric's transparency, the presence of missing/skipped items, the public URL, and the shape of the next-question payload. The only shortfall is the absence of routing context relative to sibling profile tools.

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

Parameters3/5

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

There is a single optional parameter with full schema description coverage and an enum of supported locales, so the schema already does the work. The description says nothing about the locale parameter or how it affects question generation beyond the schema's own note, which matches the baseline-3 expectation when coverage is 100%.

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 specifies the resource precisely: completion of the 'Our Team' page, with percent, missing fields, skipped fields, public URL, and the next question. It is clear what the tool reports, though it is phrased as a noun list of outputs rather than with an explicit verb like 'Get'. Sibling tools such as team_profile_get_self and team_profile_update_self are not named or differentiated, so the boundaries rely on the reader's inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this to learn what profile data is missing and what to ask next, and the closing 'Does not change anything' signals a read-only diagnostic. There is no explicit statement of when to prefer this over team_profile_get_self or when to follow it with team_profile_update_self, and no exclusions are offered.

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.

Resources