export_credentialing_report
Export the full credentialing report as CSV text (provider, credential, due date, status, follow-up history).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
credcycle
by us.artificl
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/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 burden of behavioral disclosure. It discloses the output format (CSV text) and fields, but does not mention read-only nature, permissions, rate limits, or any side effects. It provides moderate transparency but lacks safety or operational details.
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 sentence that includes the verb, resource, format, and content. Every word contributes value with no redundancy or filler.
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 the tool's simplicity (no parameters, no output schema, no annotations), the description adequately covers what it does, the format, and the contents. It could mention potential output size or encoding, but it is sufficiently complete for an export tool.
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, so the description does not need to explain parameter semantics. The description mentioning output fields is not parameter-related. Per the baseline for 0 parameters, a score of 4 is appropriate.
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?
The description clearly states the verb 'Export' plus the resource 'full credentialing report' and the output format 'CSV text', making the tool's purpose specific and distinguishable from sibling getter tools. It also lists the report's contents, leaving no ambiguity about what is exported.
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?
The description implies use for obtaining the complete report as a CSV, contrasting with siblings like get_credentialing_summary or search_credentials, but it does not explicitly state when to choose this over alternatives or any excluded situations. Guidance is implied rather than explicit.
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.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool addresses a distinct need: full export, summary totals, upcoming due list, at-risk list, and search. There is no overlap in purpose or output.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (export_, get_, list_, search_) with snake_case throughout. Predictable and easy to navigate.
Tool Count5/5
Five tools is well-scoped for a credentialing reporting server; each tool earns its place and covers a distinct aspect without redundancy.
Completeness5/5
The set covers summary, detailed queries, due-date lookups, risk identification, and full export. For a read-only reporting/query server, this is complete with no obvious gaps.