Skip to main content
Glama
Sign In
@octri/mcp

@octri/mcp

by OctriDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_sdk_methods

Read-onlyIdempotent

Retrieve ready-to-use SDK code for a specific API endpoint in all or one language, or list SDK methods by endpoint to choose the right call.

Instructions

Show how to call this API through its generated SDKs. With slug (from list_endpoints or search_docs): ready-to-use code for that endpoint in every SDK language, or in one with language (e.g. typescript, python, go). Without slug: the index of SDK methods, one line per endpoint.

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_sdk_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOne endpoint by its slug. Omit for the index of methods.
languageNoFocus on one SDK language (e.g. typescript, python, go). Omit for all supported languages.
projectIdNoProject to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • changedInput schema / properties / slug / description
      Previous value: -"Focus on a single endpoint by its slug. Omit to return all endpoints."New value: +"One endpoint by its slug. Omit for the index of methods."
  2. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare it as a safe, read-only, idempotent, open-world lookup, so the safety profile is covered. The description adds useful context the annotations do not: the two distinct output shapes (ready-to-use code samples per language vs. a one-line-per-endpoint index), which matters since there is no output schema.

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?

Three compact sentences, front-loaded with the purpose, then the two modes in a clean parallel structure. Nothing is redundant and every clause carries information.

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?

With no output schema, the description carries the burden of explaining returns and does so for both modes. The only omission is `projectId` behavior, which the schema already covers adequately.

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 baseline is 3; each parameter is already documented in the schema. The description adds marginal value by naming where `slug` comes from (list_endpoints, search_docs) and giving language examples, but it largely restates the schema's own guidance.

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?

States a specific verb and resource — 'Show how to call this API through its generated SDKs' — and immediately splits the behavior into two named modes (with slug vs. without). It does not explicitly contrast itself with the sibling list_sdks or get_endpoint, but the description of each mode is concrete enough to distinguish it in practice.

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 clear conditions: pass `slug` (sourced from list_endpoints or search_docs) to get per-endpoint code, add `language` to narrow, omit `slug` to get the method index. That is near-complete when/when-not guidance, though it never mentions sibling tools like list_sdks as an alternative for browsing SDK availability.

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