Skip to main content
Glama
Sign In
Examplary MCP Server

Examplary MCP Server

by examplary-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

me_update

Update your account details, including name and preferences, on the Examplary platform.

Instructions

Update the current user's account details.

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

Input Schema

NameRequiredDescriptionDefault
nameNoThe user's name
preferencesNoA map of user preferences

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.0.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Update', implying a write operation, but omits details like required permissions, immediacy of effects, or any side effects. This is insufficient for safe invocation.

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?

A single sentence is concise and front-loaded with the action and resource. While minimal, it avoids unnecessary words, earning a high conciseness score. Some structure improvement could include separating purpose and behavior.

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

Completeness2/5

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

The description lacks information about return values (whether the updated account is returned) and any behavioral context. For a mutation tool with no output schema, this omission makes the description incomplete for an agent to anticipate outcomes.

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 coverage is 100%, so the description adds no new meaning beyond the schema's description of name and preferences. The tool is simple, and the description does not elaborate on parameter constraints or usage, resulting in a baseline score.

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 verb 'Update' and the resource 'current user's account details', clearly distinguishing it from reading tools like me_get. However, it could be more specific about the scope of updates beyond name and preferences, though the schema fills this gap.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives such as me_get for reading or users_update for updating other users, leaving the agent without context for selection.

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

Deploy Server

Other Tools