Skip to main content
Glama
Sign In
@octri/mcp

@octri/mcp

by OctriDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_changelog

Read-onlyIdempotent

Retrieve recent API changes and breaking changes for a project, with an option to return only breaking entries.

Instructions

Get recent API changes and breaking changes

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

Input Schema

NameRequiredDescriptionDefault
projectIdNoProject to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
breakingOnlyNoOnly return entries with breaking changes (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / properties / projectId / description
      Previous value: -"Project to read. Optional — defaults to the project this server was started with. Only pass it to target a different project."New value: +"Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project."
  2. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds nothing beyond that: it does not say how far back "recent" reaches, how many entries are returned, whether results are ordered, or how breaking changes are flagged.

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 eight-word sentence with no filler and the key concept (breaking changes) front-loaded. It is efficient, though borderline under-specified rather than merely concise.

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 read-only, zero-required-parameter tool with full schema coverage and no output schema, the definition is close to sufficient. The remaining gap is the undefined recency window and result scope, which an agent would need in order to know whether this answers "what changed last week" questions.

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 description coverage is 100%, and both parameters (projectId default behavior, breakingOnly default false) are documented in the schema itself. The description's mention of "breaking changes" loosely echoes breakingOnly but adds no format or semantics beyond what the schema already states, so the baseline 3 applies.

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?

"Get recent API changes and breaking changes" gives a specific verb (get) and resource (API changelog), which is clearly distinct from the doc-lookup siblings like get_guide or search_docs. The only weakness is that "recent" is left undefined and no sibling is named, but the purpose is unmistakable.

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?

There is no statement of when to call this versus get_guide, search_docs, or get_endpoint, and no prerequisites or exclusions. The agent must infer that this is the tool for change/breaking-change questions rather than release documentation.

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