Skip to main content
Glama
Sign In

MCC Solutions

by com.mcc-solutionsnj
OverviewDiscussionsAdmin

Verify an MCC Solutions credential

verify_credential
Read-onlyIdempotent

Check a credential signed by MCC Solutions: the company's own (notary commission, E&O, certifications, from /credentials) or a contractor's clearance credential (shared by the contractor or returned by firm_order_status), including the no-personal-details version (…/clearance.jwt: yes or no for commission, E&O, background check and agreement, no name or dates). Give the credential as a compact JWT or its link on mcc-solutionsnj.com. Returns whether the signature matches the site's did:web key (so it wasn't altered), whether it's within its dates, and for contractors whether they're cleared right now.

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

Input Schema

NameRequiredDescriptionDefault
credentialYesThe vc+jwt text, or a link like https://mcc-solutionsnj.com/credentials/contractors/<id>.jwt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the bar is lower, and the description still adds real value: it explains what the result means (signature match against the site's did:web key proving no alteration, date-window validity, and live contractor clearance status). It also flags the privacy variant that carries only yes/no answers with no name or dates, which an agent needs to interpret output correctly.

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?

Purpose and accepted inputs are front-loaded, and the second sentence cleanly states the three things returned. The first sentence is long and stacks parentheticals (notary commission, E&O, certifications; no name or dates), making it denser than necessary, though no sentence is 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?

With one fully documented parameter and no output schema, the description carries the return-value burden well by naming signature validity, date validity, and contractor clearance status. Minor gaps remain around the exact result shape (fields, error behavior for an unparsable or non-MCC credential).

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?

Schema coverage is 100%, so the parameter is already documented, but the description adds meaning about what counts as a valid credential — the compact vc+jwt form, an mcc-solutionsnj.com link, and the no-personal-details clearance.jwt variant. That goes modestly beyond the schema's example URL.

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?

Opens with a specific verb and resource ('Check a credential signed by MCC Solutions') and immediately enumerates the two credential families it accepts: the company's own documents from /credentials and a contractor's clearance credential from sharing or firm_order_status. An agent can distinguish this from sibling firm_order_status, which supplies credentials rather than verifying them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description establishes clear applicability: it names the credential sources (company /credentials page, contractor-shared, firm_order_status output) and the accepted input forms (compact JWT or mcc-solutionsnj.com link). It stops short of explicit exclusions or a direct 'use X instead when...' routing statement against siblings, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MCC Solutions toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources