Skip to main content
Glama
Sign In
io.github.CE-RISE-software/dpawb

io.github.CE-RISE-software/dpawb

Official
by CE-RISE-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Template

template

Retrieve a bundled YAML template for SHACL-based assessment of digital passport data models. Choose from profile, use_case, or alignment templates.

Instructions

Return one bundled YAML template document.

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": {
      "name": "<name>"
    },
    "name": "template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are present, and the description fails to disclose any behavioral traits (e.g., read-only, error handling, side effects). For a retrieval tool, it does not state if it modifies state or requires specific permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (one sentence) and front-loaded, but it sacrifices necessary detail. It is not overly verbose, but the extreme brevity undermines its usefulness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (one enum parameter, no output schema), the description should still explain what templates are and how the 'name' parameter selects them. It is incomplete for effective tool use.

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

Parameters1/5

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

The description does not mention the 'name' parameter or its enum values ('profile', 'use_case', 'alignment'). With 0% schema description coverage, the agent gets no additional meaning beyond the raw schema, which is insufficient for correct invocation.

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 states the verb 'Return' and the resource 'one bundled YAML template document', making the basic purpose understandable. However, it does not differentiate from sibling tools like 'schema' or 'vocabulary', which could also return documents.

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?

No guidance is provided on when to use this tool versus its siblings (e.g., 'schema', 'coverage'). The description lacks context for selection, such as prerequisites or typical use cases.

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