Skip to main content
Glama
Sign In
Veyline MCP Server

Veyline MCP Server

by Payloadhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

veyline_status

Reads the authenticated organization’s current entitlement and tier to check access limits before payment decisions, without authorizing a payment.

Instructions

Read the current authenticated organization Veyline entitlement and tier. Does not authorize a payment. (Rail A2A skill veyline_status.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the operation is a read and does not authorize a payment, but it omits details such as authentication requirements, error behavior, and return structure beyond 'entitlement and tier.'

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?

The description is two short sentences and front-loads the core action. The parenthetical internal skill reference is slightly unnecessary but does not distract materially.

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?

For a simple zero-parameter read tool, the description covers purpose and read-only behavior. However, with no output schema it could say more about what 'entitlement and tier' means or what happens when the organization is not authenticated.

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 there is no parameter semantics burden. The baseline for zero-parameter tools is 4, and nothing in the description undermines that.

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 states a specific verb ('Read') and resource ('current authenticated organization Veyline entitlement and tier'), making the tool's purpose clear. It does not explicitly differentiate itself from siblings like veyline_usage or veyline_preflight, but the resource scope is distinct enough.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no when-not conditions, and no named alternatives. The note 'Does not authorize a payment' clarifies a boundary but does not help an agent choose between this tool and its siblings.

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