Skip to main content
Glama
nohosa001-pixel

security-gate-x402

by nohosa001-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_agent_credit_rating

Retrieve a FICO-style credit score, investment grade, and uncollateralized lending capacity for an AI agent from on-chain performance using its EVM wallet address.

Instructions

Retrieves dynamic FICO-style credit score (300-850), investment grade (AAA-D), and uncollateralized lending capacity for an autonomous AI agent based on on-chain history and performance. Use this tool ONLY to evaluate the financial creditworthiness, FICO-style credit score (300-850), investment grade (AAA-D), and uncollateralized lending capacity of an autonomous AI agent by its EVM wallet address. Do NOT use this tool for security, injection, or code auditing; use the respective security inspection tools instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_addressYesChecksummed EVM wallet address (0x...) of the autonomous agent to query.0x71C637024457bb52792e55106d80a3E70d8a5944

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.5

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions the dynamic nature and on-chain history basis, but does not disclose read-only nature, error handling, or any side effects. Adds some behavioral context but not comprehensive.

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?

Two sentences, main purpose front-loaded. Second sentence repeats some terms (FICO-style, investment grade, lending capacity) and adds usage guidance; somewhat redundant but still efficient.

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?

Simple one-parameter retrieval tool with no output schema. Description enumerates the three returned components and includes clear use/exclusion guidance, making it adequate for agent invocation.

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

Parameters3/5

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

Schema description coverage is 100% with a clear, detailed description of the agent_address parameter. The tool description adds no extra parameter meaning beyond the schema, which is acceptable given full coverage.

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?

States a specific verb 'Retrieves' with resource 'credit rating' and enumerates exact outputs (FICO score, investment grade, lending capacity). Explicitly distinguishes from security-focused siblings by naming them as alternatives.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('ONLY to evaluate financial creditworthiness') and when-not-to-use ('Do NOT use for security, injection, or code auditing') with references to respective security inspection tools.

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