Skip to main content
Glama
Sign In
Glyphic

Glyphic

by MS-Teja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_schema

Retrieve the JSON schema of the DiagramInput payload to identify supported diagram types and their properties.

Instructions

Returns the JSON schema of the DiagramInput payload to help the AI understand supported diagram types and properties.

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_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states return of JSON schema, but doesn't disclose any behavioral traits (e.g., read-only, no side effects, auth requirements).

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?

Single sentence, 19 words, front-loaded with main action. Every word provides value; no unnecessary repetition.

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?

Given no output schema, description explains return value (JSON schema of DiagramInput) and purpose (supported types/properties). Sufficient for a simple tool, though more detail on structure could help.

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?

Zero parameters, baseline score of 4. Description adds context about the schema's purpose, but no parameter details needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states verb 'returns', resource 'JSON schema of the DiagramInput payload', and purpose 'help the AI understand supported diagram types and properties'. Distinguishes from sibling 'render_diagram'.

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?

Implies use before calling render_diagram, but lacks explicit when-to-use or alternatives. No direct guidance on when not to use.

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