Skip to main content
Glama
Sign In

Revly

by no.revly
OverviewDiscussionsAdmin

Tilkoblingskontekst fra Revly

revly_kontekst
Read-onlyIdempotent

Viser firmaet tilkoblingen gjelder (ID og navn), rollen din, den registrerte assistenten og verktøyene du har tilgang til.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
clientNoAssistant registered for this connection.
statusYesavailable when the connection is valid.
firma_idNoID of the firm this connection is for, as text.
firma_navnNoName of the firm this connection is for.
firma_rolleNoYour role in the firm, for example partner.
operation_idYesRevly operation ID for this read, recorded in the access log.
allowed_toolsNoRead tools this connection may call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds value beyond that by naming exactly what slice of state is revealed (company, role, assistant, tool access), which tells the agent this is a cheap non-mutating identity lookup. It does not mention caching or rate behavior, but nothing about the call is risky enough to require it.

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?

A single sentence, front-loaded with the primary return value (the company) and then the secondary context fields. No filler, no repetition of the title.

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?

An output schema exists and the description enumerates the payload fields, so return values need no further explanation. The only mild gap is the absence of guidance on when in a workflow to call it, but for a zero-argument, read-only context tool the definition is otherwise sufficient to invoke correctly.

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 schema takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the tool is parameterless by describing pure server-side context retrieval.

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 of disclosure ('Viser') plus an enumerated set of resources: company (ID and name), your role, the registered assistant, and available tools. That is concrete enough to distinguish it from the sibling 'hent_*' tools, which fetch domain data rather than connection metadata. It stops short of a crisp one-line identity statement, but the agent can tell what it returns.

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?

The nature of the tool (connection context) implies it is a bootstrap/introspection call to make before other calls, but the description never states that explicitly, nor does it name an alternative or an exclusion. Usage is inferable rather than prescribed.

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

All Revly 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