Skip to main content
Glama

Vistas Studio: generative SVG art for agents

Check a Studio Pass (free)

pass_status
Read-onlyIdempotent

FREE. Whether a Studio Pass is valid, its tier and when it expires.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pass": "<pass>"
    },
    "name": "pass_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
passYesThe pass (mp1....).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and a closed-world scope, so the safety profile is covered. The description adds the cost signal ('FREE') and states the returned fields, which are not in any structured field. It does not say what happens for an invalid or expired pass, or whether any authentication is required.

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?

One short sentence fragment with zero padding; the cost flag and the returned fields are front-loaded. It is slightly clipped to the point of being ungrammatical, but nothing in it 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?

For a one-parameter read-only lookup with no output schema, stating the three things it returns (validity, tier, expiry) fills the main gap. The missing piece is failure/expiry edge-case behavior, which is minor for a free status check.

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

Parameters3/5

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

Schema coverage is 100% and the single 'pass' parameter already carries its own description with the 'mp1....' format hint. The description adds nothing about the parameter, so the baseline 3 applies.

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 the resource (Studio Pass) and enumerates exactly what the tool reports: validity, tier, and expiry. That is unambiguous as to what the call returns, but it is a noun phrase with no verb and makes no attempt to distinguish itself from siblings like buy_studio_pass or redeem_pass.

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 when-to-use guidance at all. The 'FREE' prefix hints that cost is a consideration, but the description never says to use this before redeeming, or how it differs from buy_studio_pass or redeem_pass, leaving the agent to infer the workflow position.

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