ServiceNow MCP Server

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

No annotations are provided, so the description carries full burden. It mentions 'Commit' which implies a write/mutation operation, but doesn't disclose behavioral traits like whether this is destructive, requires specific permissions, has side effects, or what happens post-commit. This is inadequate for a tool that likely alters system state.

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

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

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and context, making it easy to parse quickly, though this brevity contributes to other deficiencies.

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

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

Given no annotations, no output schema, and 0% schema description coverage for a mutation tool, the description is incomplete. It lacks essential context like what 'commit' entails, expected outcomes, error conditions, or how it differs from similar tools, making it insufficient for reliable agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds no parameter information beyond what's implied by the tool name. The schema defines 'changeset_id' and optional 'commit_message', but the description doesn't explain their roles, formats, or constraints, leaving gaps in understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Commit') and target ('a changeset in ServiceNow'), which provides a basic purpose. However, it's vague about what 'commit' means operationally and doesn't distinguish from sibling tools like 'publish_changeset' or 'update_changeset', leaving ambiguity about when to use each.

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

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

No guidance is provided on when to use this tool versus alternatives. With siblings like 'publish_changeset', 'update_changeset', and 'create_changeset', the description fails to specify prerequisites, sequencing, or exclusions, leaving the agent to guess based on tool names alone.

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