Skip to main content
Glama
SP6 MCP

SP6 MCP

by HANJUSON

sp6_object_find

Read-onlyIdempotent

Find Programs or Multis by case-insensitive name query in an SP6 file and resolve matching names to IDs.

Instructions

Find Programs or Multis whose name contains query (case-insensitive) in a file.

Use this to turn names such as "Prophet Pad" into IDs. Names come only from the given file; factory names are not bundled with this server.

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": {
      "path": "<path>",
      "query": "<query>"
    },
    "name": "sp6_object_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoprogram
pathYes
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety bar is covered. The description adds behavior beyond that: matching is a case-insensitive substring of the name, and the lookup pool is limited to the file, with no factory names. It does not disclose result truncation or ordering, even though a 'limit' parameter with a default of 20 exists.

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?

The definition is three short sentences, front-loaded with the core operation and then the purpose and scoping caveat. There is slight redundancy in the final sentence ('names come only from the given file' and 'factory names are not bundled'), but nothing is wasted overall.

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?

For a simple find tool with no output schema, the definition sets up the purpose, matching rule and name-source scope. It omits the shape of the results (the IDs implied by 'turn names into IDs') and all truncation and pagination behavior via 'limit', which are the main gaps an agent would need to call it correctly.

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 carry parameter meaning. It covers 'query' (a case-insensitive name substring) and 'path' (the file searched), but it never explains 'limit', including its default of 20 and what happens when results are truncated. It also leaves 'kind' implicit; the phrase 'Programs or Multis' hints at the enum but never says that it selects between them.

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 gives a concrete verb and resource: it finds Programs or Multis by name in a given file, and it states that matching is case-insensitive substring matching. An agent can tell exactly what this tool does. It does not explicitly contrast itself with siblings, but no sibling is a finder, so the gaps are minor.

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?

It gives a clear usage trigger: 'Use this to turn names such as "Prophet Pad" into IDs.' It also states a boundary: names come only from the given file, and factory names are not bundled. It does not say when not to use it or how to choose between kind values, but the intended use case is unambiguous.

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