Skip to main content
Glama
Sign In

Arrumou Neural

by io.github.brunoreisportela
OverviewDiscussionsAdmin

Catálogo de capacidades

get_capabilities
Read-onlyIdempotent

Lista todas as operações disponíveis nesta versão com escopo, risco, pré-requisitos, efeitos colaterais e se estão utilizáveis para esta autorização.

Escopo: profile:read · Risco: read · Efeitos: Nenhum.

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

Input Schema

NameRequiredDescriptionDefault
familyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The description adds useful behavioral context beyond the annotations, especially the required scope 'profile:read' and the statement that there are no effects. The risk and no-effects statements are partly redundant with readOnlyHint and destructiveHint=false, but the scope requirement is valuable.

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?

The description is compact and front-loaded: one sentence describes the catalog contents, followed by a short metadata line for scope, risk, and effects. There is no evident waste.

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?

The description explains what the returned catalog contains and its authorization context, which is helpful. However, with no output schema and no schema description coverage, it should at least clarify the optional 'family' filter and ideally the return shape or pagination behavior.

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

Parameters2/5

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

Schema description coverage is 0% for the single optional 'family' parameter, and the description never mentions it. The only mitigating factor is that the parameter is optional, so the tool can still be invoked without it, but filtering semantics are opaque.

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 clearly states the verb and resource: it lists all operations available in this version, including scope, risk, prerequisites, side effects, and authorization usability. The purpose is understandable, but it does not explicitly distinguish itself from sibling tools such as get_permissions or get_identity.

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: the tool appears intended for discovering which operations are available and usable for the current authorization. There is no explicit 'use this when' guidance, no exclusions, and no named alternatives.

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

All Arrumou Neural toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources