First AI Employee

Get available capabilities

get_capabilities

Read-onlyIdempotent

Read-only metadata listing for the connected workspace. Accepts an empty object and returns available capability identifiers, names of separately exposed MCP tools, and the write-gate state after live permission checks. It never invokes, prepares, approves, or commits another operation. To perform an operation, call its separately listed tool with that tool input schema.

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

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`request_id`	Yes
`schema_version`	Yes
`writes_enabled`	Yes
`available_tool_names`	Yes
`available_capabilities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results reflect 'live permission checks,' expose 'the write-gate state,' and this tool performs no side effects on other operations. The return-value detail is partially redundant with the output schema, keeping it just short of a 5.

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 sentences, front-loaded with the resource and return contents, then the negative boundary, then the forward pointer. No filler or restatement of the name.

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 rich annotations, a full output schema, and no parameters, the description covers everything needed to call it correctly. The one gap is the absence of any relational context versus its single sibling, which matters slightly for tool selection in a two-tool namespace.

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?

There are zero parameters and the schema has additionalProperties false with an empty properties object, which is self-evident. The description's note that it 'accepts an empty object' adds a small confirming touch to the schema and is the appropriate baseline for a no-param tool.

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 names a specific verb and resource ('read-only metadata listing for the connected workspace') and enumerates what it returns: capability identifiers, names of separately exposed MCP tools, and write-gate state. It does not, however, distinguish itself from its sibling get_business_identity, so an agent must infer that distinction.

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?

It clearly states the boundary — 'It never invokes, prepares, approves, or commits another operation' — and routes the agent onward: 'To perform an operation, call its separately listed tool with that tool input schema.' That is strong when-to-use/when-not guidance, but no guidance is given for choosing between this and get_business_identity.

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

All First AI Employee tools Inspect

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

Need Help?