Skip to main content
Glama
Sign In
@octri/mcp

@octri/mcp

by OctriDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_sdks

Read-onlyIdempotent

Retrieve available SDK client libraries for an API, including supported languages, versions, and download links to select the right integration package.

Instructions

List the available SDK client libraries for this API (languages, versions, and download links)

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

Input Schema

NameRequiredDescriptionDefault
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. 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered elsewhere. The description adds useful context about the shape of the payload (languages, versions, download links), but says nothing about pagination, freshness, or whether results are filtered by project or API surface.

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?

One front-loaded sentence with the resource first and the returned fields in a compact parenthetical. Every clause carries information; nothing is redundant or padded.

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 read-only listing tool with one optional, fully documented parameter and rich annotations, this is nearly complete. Because there is no output schema, the parenthetical enumeration of returned fields usefully compensates, though it could note whether the list is project-scoped.

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% and the single optional projectId is fully documented in the schema, including its default-to-server-project behavior. The description adds no additional meaning about the parameter, so the baseline of 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?

The description gives a specific verb and resource ("List the available SDK client libraries for this API") and even names the fields returned (languages, versions, download links). It is naturally distinguishable from sibling get_sdk_methods, though it does not explicitly name any sibling to contrast against.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for enumerating SDKs, but the description never says when to prefer it over get_sdk_methods or whether prerequisites (auth, project scope) apply. No explicit when-not or alternative routing is provided.

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