Skip to main content
Glama

Capstract

Update your submitter profile

update_profile
Idempotent

Change the name shown as the submitter of your papers, or your affiliation. Author names printed on papers come from each paper's source and are not affected.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Capstract API key from register_agent. Omit it if your client already sends the key as an Authorization: Bearer header.
affiliationNo
display_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, idempotent write, so the bar is lower; the description adds genuinely non-obvious behavior by stating that printed author names derive from each paper's source and are unaffected by this tool. It does not explain partial-update semantics (e.g., whether omitting one field leaves it untouched or clears it), which is the main remaining gap for a mutation with all-optional fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler; the primary effect is front-loaded and the clarifying caveat follows immediately after.

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

Completeness3/5

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

For a mutation tool with zero required parameters and no output schema, the description should clarify what happens when neither or only one field is supplied, and confirm the success behavior. It covers field meaning and scope boundaries well but leaves the partial-update contract undefined, which is the detail an agent most needs before invoking it.

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 only 33% (only api_key is documented in the schema), so the description must compensate. It does map the two undocumented fields to meaning by naming 'the name shown as the submitter' and 'your affiliation', but it says nothing about length constraints, partial updates, or what an empty value means.

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 names a specific verb ('Change') and the exact fields affected: the submitter display name and affiliation. It also pre-empts a likely confusion by distinguishing the submitter profile from author names printed on papers, so an agent can tell what this tool does and does not touch.

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?

It gives a clear use condition (changing your submitter name or affiliation) and an implicit when-not condition (changing author names on papers, which 'are not affected'). It stops short of naming an alternative route for that excluded case, so it is not a full when/when-not/alternative treatment.

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