Skip to main content
Glama

Connected service capabilities

vault_services
Read-onlyIdempotent

List granular OAuth-connected service capabilities explicitly granted to this AI, including safe metadata for the user's bound repositories, projects, and other provider resources.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds context the annotations do not: results are restricted to capabilities 'explicitly granted' to this AI and contain only 'safe metadata', signalling that unreturned services are ungranted and that no secrets are exposed.

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?

It is a single front-loaded sentence with the object of the call stated first and no filler. 'Granular' is a slightly soft qualifier, but nothing in the sentence is wasted.

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?

There is no output schema, so the description must convey the shape of the return value; it does so conceptually as a list of granted capabilities with safe metadata about bound repositories and projects. Per-item field detail is absent, but that is acceptable for a zero-parameter discovery tool.

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

Parameters4/5

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

The tool takes zero parameters, so the schema carries nothing an agent must interpret and the baseline of 4 applies. The description correctly adds no parameter guidance, which would have been noise.

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 uses a specific verb ('List') plus a well-scoped resource ('OAuth-connected service capabilities explicitly granted to this AI'), and the phrase 'bound repositories, projects, and other provider resources' tells the agent what data is covered. It never differentiates itself from near-neighbours like vault_capabilities or vault_connections, so an agent cannot rule those out from the text alone.

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 it should call this to discover which provider services it has been granted. There is no explicit when-to-use, no when-not-to-use, and no reference to the sibling discovery tools, which is a real gap given several similarly named options.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources