Skip to main content
Glama

freedom-mcp

by com.getfreedomos
OverviewDiscussionsAdmin

Update reader profile

update_reader_profile
Destructive

Update a person's OPERATOR FLUENCY (baseline + per-topic strengths that follow them across companies). Use when the operator (or an admin) sets or corrects how agents should speak to them, or when seeding an empty profile with seed_if_empty for a first guess. Human door for edits; agents may seed empty self only.

[write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time. Call it on the first clear ask; the card is the yes — do not re-ask in chat.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsNoTopic → novice|fluent|expert (merged).
companyIdYesFreedomOS company id to act within (you must be a member). Required for company-scoped tools.
member_idNoOptional target UUID. Defaults to you. Updating another member requires admin in this company.
default_levelNo
glossary_seenNoGlossary terms already introduced to this person (full replace, not merged).
seed_if_emptyNoIf true, agents may write only when the target has no profile yet (self only). Human doors may always write.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / glossary_seen / description
      Added value: +"Glossary terms already introduced to this person (full replace, not merged)."
    • changedInput schema / properties / member_id / description
      Previous value: -"Optional target UUID. Defaults to you."New value: +"Optional target UUID. Defaults to you. Updating another member requires admin in this company."
  2. Changed5 schema fields changed
    • removedInput schema / properties / default_level / description
      Removed value: -"Baseline expertise for domains not explicitly listed."
    • changedInput schema / properties / domains / description
      Previous value: -"Per-domain expertise map, e.g. { \"797_compliance\": \"expert\", \"seo_aeo\": \"novice\" }. Merged into the existing map."New value: +"Topic → novice|fluent|expert (merged)."
    • removedInput schema / properties / glossary_seen / description
      Removed value: -"Jargon terms already glossed for this reader (replaces the list)."
    • changedInput schema / properties / member_id / description
      Previous value: -"Optional UUID of the member to update. Defaults to the caller. A non-self target requires you to be a company admin/owner."New value: +"Optional target UUID. Defaults to you."
    • addedInput schema / properties / seed_if_empty
      Added value: +{
+  "description": "If true, agents may write only when the target has no profile yet (self only). Human doors may always write.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description doesn't need to restate mutation semantics. It adds valuable context beyond annotations: write-tier approval behavior, the human-door edit policy, and the instruction to call once on a clear ask without re-asking. No contradiction with annotations.

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 core purpose is front-loaded in a single dense sentence, and the bracketed approval block earns its place because it governs how the tool should be invoked. Slightly jargon-heavy phrases like 'the card is the yes' keep it from being perfectly crisp.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 6 parameters, one required, and no output schema, this description covers purpose, usage triggers, permission boundaries, approval flow, and the seed-only edge case. Remaining details like member_id admin requirements and glossary full-replace behavior are already present in the schema.

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 83%, so the schema already handles most parameter meaning. The description adds value by tying 'baseline' to default_level, 'per-topic strengths' to domains, and giving seed_if_empty a concrete scenario: seeding an empty profile for a first guess.

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: updating a person's OPERATOR FLUENCY profile, including baseline and per-topic strengths that follow them across companies. This clearly distinguishes it from company-scoped profile tools like update_my_profile or update_voice_profile.

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?

Explicitly says when to use it: when an operator or admin sets/corrects how agents should speak, or when seeding an empty profile with seed_if_empty. It also gives when-not guidance by restricting agents to seeding empty self only and marking edits as a human door.

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

All freedom-mcp toolsInspect
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