Skip to main content
Glama

get_security_risk_endpoints

Identify and analyze security risks in blockchain transactions by retrieving endpoints for token security, NFT verification, phishing detection, and smart contract vulnerabilities.

Instructions

Get all endpoints in the "Security & Risk Analysis" category. Comprehensive security endpoints for token security analysis, NFT authenticity verification, honeypot detection, malicious address identification, phishing site detection, contract approval risks, dApp security assessment, ABI data decoding, and comprehensive security metrics to protect users from scams, rugpulls, and malicious contracts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'get_security_risk_endpoints' tool. Dynamically generated for each category, it fetches the tools in the 'Security & Risk Analysis' category using getAllToolsInCategory and returns a formatted list with names and descriptions.
    handler: async (
      args: Record<string, unknown> | undefined,
    ): Promise<any> => {
      const toolsInCategory = getAllToolsInCategory(category.category);
      
      return asTextContentResult({
        category: category.category,
        description: category.description,
        tools: toolsInCategory.map((tool ) => ({
          name: tool.name,
          description: tool.description
        })),
      });
    },
  • Registration of the 'get_security_risk_endpoints' tool as the name of the 'Security & Risk Analysis' category in ToolRegistry. This category definition is used by dynamicTools to create the MCP tool.
    {
      "category": "Security & Risk Analysis",
      "name": "get_security_risk_endpoints",
      "description": "Comprehensive security endpoints for token security analysis, NFT authenticity verification, honeypot detection, malicious address identification, phishing site detection, contract approval risks, dApp security assessment, ABI data decoding, and comprehensive security metrics to protect users from scams, rugpulls, and malicious contracts.",
      "tools": [
        "get_token_security",
        "get_nft_security",// rishabh
        "check_malicious_address",// rishabh
        "check_approval_security",// rishabh
        "get_user_approvals",// rishabh
        "check_dapp_security",// rishabh
        "detect_phishing_site",// rishabh
        "decode_abi_data",// rishabh
      ]
    },
  • Tool definition including name 'get_security_risk_endpoints', description, and empty inputSchema (z.object({})) for the dynamically generated category tool.
    },
    tool: {
      name: categoryEndpointName,
      description: `Get all endpoints in the "${category.category}" category. ${category.description}`,
      inputSchema: zodToInputSchema(categorySchema),
  • Helper function getAllToolsInCategory used by the handler to retrieve the list of supported tools matching the names in the category's 'tools' array.
    export function getAllToolsInCategory(category: string){
      let categoryUsed = ToolRegistry.find(tool => tool.category === category);
      if(!categoryUsed){
        return []
      }
      const allWrappedTools = supportedTools
      // return all the tools from wrapped tools that are in the category (name match)
      let toolsInCategory = [];
      for (const tool of categoryUsed.tools){
        const wrappedTool = allWrappedTools.find(wrappedTool => wrappedTool.name === tool);
        if(wrappedTool){
          toolsInCategory.push(wrappedTool);
        }
        else console.log(`Tool ${tool} not found in wrapped tools`);
      }
      return toolsInCategory;
    }
  • Dynamic generation of category tools (including 'get_security_risk_endpoints') from ToolRegistry, defining metadata, tool spec, and handler.
    const categoryTools = ToolRegistry.map(category => {
      const categorySchema = z.object({});
      
      const categoryEndpointName = category.name;
      
      return {
        metadata: {
          resource: 'dynamic_tools',
          operation: 'read' as const,
          tags: ['category'],
        },
        tool: {
          name: categoryEndpointName,
          description: `Get all endpoints in the "${category.category}" category. ${category.description}`,
          inputSchema: zodToInputSchema(categorySchema),
        },
        handler: async (
          args: Record<string, unknown> | undefined,
        ): Promise<any> => {
          const toolsInCategory = getAllToolsInCategory(category.category);
          
          return asTextContentResult({
            category: category.category,
            description: category.description,
            tools: toolsInCategory.map((tool ) => ({
              name: tool.name,
              description: tool.description
            })),
          });
        },
      };
    });
    
    return [getEndpointTool, callEndpointTool, ...categoryTools];
Behavior2/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 implies a read operation ('Get') but doesn't disclose behavioral traits such as authentication needs, rate limits, pagination, or response format. The list of security topics adds context but not 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.

Conciseness3/5

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

The description is front-loaded with the core purpose but becomes verbose with a lengthy list of security topics. Sentences like 'Comprehensive security endpoints for token security analysis...' could be condensed or structured as bullet points for better clarity.

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 no annotations and no output schema, the description is incomplete. It lacks details on what the tool returns (e.g., endpoint list format, metadata) and operational constraints, which are critical for an agent to use it effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately omits parameter details, maintaining focus on the tool's purpose without redundancy.

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 tool's purpose: 'Get all endpoints in the "Security & Risk Analysis" category.' It specifies the verb ('Get') and resource ('endpoints'), and distinguishes from siblings by focusing on security endpoints. However, it could be more specific about what 'get' entails (e.g., list, retrieve details).

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It mentions the category but doesn't compare to sibling tools like 'get_token_contract_endpoints' or 'get_nft_analytics_endpoints', leaving the agent to infer usage based on category alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hive-intel/hive-crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server