Skip to main content
Glama

UpdateProposalTitle

DestructiveIdempotent

Change the title of a schema proposal, the same action as renaming a proposal in GraphOS Studio. Returns the proposal's ID and new title, or an error with a message. Provide the graph ID, the proposal variant name from GetProposal, and the new title.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "graphId": "<graphId>",
      "proposalVariant": "<proposalVariant>",
      "title": "<title>"
    },
    "name": "UpdateProposalTitle"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
graphIdYes
proposalVariantYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorsNo
extensionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds the success/error response shape and the Studio equivalence, but never explains why the operation is destructive — e.g. that the previous title is overwritten with no undo, or what permissions/roles are required.

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?

Three short sentences, front-loaded with purpose and followed by the return contract and the parameter checklist; nothing is padded. The return-value sentence partially duplicates the output schema, which keeps it from a 5.

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 three-parameter mutation with an output schema and rich annotations, the description covers purpose, prerequisite lookup, and invocation inputs — enough to call it correctly. The remaining gap is behavioral edge cases (permissions, overwrite semantics) rather than anything blocking a correct call.

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?

With 0% schema description coverage the description has to carry the parameters, and it names all three (graph ID, proposal variant name, new title) while explaining the non-obvious source of proposalVariant from GetProposal. It leaves the graphId format ambiguous (graph ref vs. opaque ID) and says nothing about title constraints such as length or uniqueness.

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 ("Change the title of a schema proposal") and ties it to a concrete analogue (renaming in GraphOS Studio), which cleanly separates it from UpdateProposalDescription, UpdateProposalStatus, and UpdateProposalReviewers. An agent can identify the tool without opening the 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 an explicit prerequisite workflow: fetch the proposal variant name via GetProposal before calling, plus the required graph ID and new title. It does not state when to avoid this tool or what happens if the proposal is in a non-editable state, so it stops short of full alternative/exclusion guidance.

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