Skip to main content
Glama
Sign In
json-chamber-mcp

json-chamber-mcp

by Slid-Phi-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

chamber_status

Check license status to determine if evaluation hours remain, purchase is active, or the license has expired.

Instructions

License status: eval remaining hours, purchased, or dead.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the possible output values but does not explicitly state that the operation is read-only or side-effect-free, nor does it mention any permissions or rate limits. This is a minimal disclosure that leaves safety posture implicit.

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?

The description is a single, front-loaded phrase that packs the core resource and possible states into eight words without any filler. Every token earns its place, and the structure leads with the topic 'License status'.

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 zero-parameter tool with no output schema, the description conveys the essential return values, which is adequate for basic invocation. However, it omits context about when to choose this over chamber_info and leaves terms like 'eval' and 'dead' under-specified, making the completeness only partially sufficient.

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 has zero parameters, and the schema coverage is 100% (empty object), so there are no inputs to document. Per the baseline for 0 parameters, this is fully adequate; the description adds no parameter semantics but none are needed.

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 clearly identifies the resource (license status) and enumerates the possible states (eval remaining hours, purchased, or dead). It conveys a query-like purpose and distinguishes itself from siblings like chamber_info by being specifically about license status, though it lacks an explicit verb like 'get' or 'check'.

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?

The description implies use when license status is needed, but it provides no explicit when-to-use guidance, no exclusions, and no comparison to sibling tools such as chamber_info or benefit_check. An agent is left to infer when this tool should be selected over alternatives.

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