Skip to main content
Glama
Sign In
mcp-contract-security

mcp-contract-security

by mastrophot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

compare_security_models

Compare NEAR and Ethereum security architectures to assess risk profiles and choose a safer smart contract model.

Instructions

Compare NEAR vs Ethereum security architecture and risk profile.

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": "compare_security_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNosolidity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description itself must convey behavioral traits. It accurately conveys a read-only comparison action, but it does not explain what output to expect, how the language parameter affects behavior, or whether this is an educational reference versus an active security analysis.

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, focused sentence with no redundancy. It front-loads the core purpose and avoids unnecessary elaboration.

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

Completeness3/5

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

The tool is relatively simple, but the optional language parameter has no clarifying context in the description, and there is no output schema to fill in return-value expectations. The description is adequate for a high-level comparison tool but leaves the parameter's role and output format unexplained.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not mention the language parameter. The enum values rust/solidity/typescript are self-descriptive as programming languages, but why a language choice matters for comparing NEAR vs Ethereum security models is left unexplained.

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 tool's specific action ('compare') and target ('NEAR vs Ethereum security architecture and risk profile'). It is distinct from sibling tools like scan_contract and audit_checklist, which imply per-contract inspection rather than a high-level architectural comparison.

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 given for when to use this tool versus scan_contract or audit_checklist. The intended usage is only implied by the description's comparative focus; there are no explicit when/when-not conditions or alternative tool references.

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