Skip to main content
Glama
Sign In
llm-toolkit

llm-toolkit

by 0x1Jar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Payloads

get-payloads

Retrieve payloads from a JSON file, filtering by category, context, or risk level for security testing.

Instructions

Fetch payloads from a JSON file with optional filters (category, context, riskLevel)

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": {
      "filepath": "<filepath>"
    },
    "name": "get-payloads"
  }
}

Input Schema

NameRequiredDescriptionDefault
filepathYes
filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behaviors. It states 'Fetch' implying a read operation, but lacks details on safety, side effects, or error conditions. The minimal description does not adequately inform about potential risks or guarantees.

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 sentence of 13 words, containing only relevant information. It is appropriately sized and front-loaded with the verb and resource.

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 the lack of annotations and output schema, the description is insufficient. It does not explain return format, error behavior, or provide enough context for a user to understand the tool's full functionality, especially with several related sibling tools.

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%, so the description must explain parameters. It only lists the filter names 'category, context, riskLevel' without describing their semantics, valid values, or how they affect the fetch. The required 'filepath' parameter is not described at all.

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 'Fetch' and resource 'payloads from a JSON file', and mentions optional filters. It distinguishes itself from sibling tools like 'generate-payload' (creation) and 'analyze-payload' (analysis) by indicating it is a retrieval operation.

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 explicit guidance on when to use this tool versus alternatives. The description only implies usage for fetching filtered payloads but does not provide context or exclusions.

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