Skip to main content
Glama

Draft the team profile from the website

draft_team_profile

Draft a team profile from the company's website and any notes from your person. Returns a draft and its sources; nothing is saved. Walk your person through it — name as spoken, product names, tone, words to use and avoid, house rules, the knock line — and save what they approve with set_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": "draft_team_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoWhat your person said about how the crew should sound.
websiteNoCompany website, if known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Adds real value beyond the annotations by describing the return ('a draft and its sources') and the review checklist the agent should walk through (name as spoken, product names, tone, words to use and avoid, house rules, the knock line). However, 'nothing is saved' sits in mild tension with readOnlyHint=false — whether a draft record persists, whether the site is crawled live, and what happens if website is omitted are all left unresolved, which matters for a tool that hits an external URL.

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 purpose and followed by the save hand-off. The second sentence is a dense run-on checklist but every element in it is actionable, so little is wasted; it could be split for readability without losing content.

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?

There is no output schema, and the description compensates by stating that a draft plus its sources come back. Tool complexity is low (2 optional params, no nested objects), and the review-then-save loop is spelled out. Only the no-input case (neither notes nor website supplied) is left unexplained.

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?

Schema description coverage is 100% and both parameters are optional, so the schema already carries the param semantics. The description adds only light framing ('notes from your person', 'the company's website'), with no detail on fallback behaviour when website is absent or what shape notes should take. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Draft a team profile') plus the inputs it draws on (the company website, notes from your person), and immediately distinguishes itself from the saving sibling by noting 'nothing is saved' while naming set_team_profile as the persist step. An agent can tell this apart from get_team_profile and set_team_profile without opening a 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?

Gives a clear workflow context: draft first, 'walk your person through it', then 'save what they approve with set_team_profile' — an explicit alternative with the condition that selects it. It stops short of stating when not to use it (e.g., when a profile already exists and should be edited directly), so it falls just short of the top band.

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.