Skip to main content
Glama
magicsword-mcp

magicsword-mcp

Official

List available intelligence sources

list_intel_sources
Read-onlyIdempotent

Discover global and organization-owned intelligence sources and their IDs, filter by platform or enabled status, and select sources to attach to a policy.

Instructions

Discovers global and organization-owned intelligence sources and their IDs for attaching to a policy. Returns enabled sources by default; is_enabled=false lists disabled sources. Filter by the policy platform. Includes creation, update, sync, and last successful collection check timestamps when available; unknown dates remain unknown. Use list_policies to find the policy ID, then manage_policy_intel_sources action=list to inspect attachments or action=attach with the selected source_ids. Premium sources may require a paid plan. Requires intel:read.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
platformNo
is_enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive semantics, and the description adds real context beyond them: default enabled-only filtering, included timestamp fields, unknown-date handling, a premium-plan caveat, and the intel:read scope requirement. The only meaningful gap is that pagination behavior for limit/offset is never described.

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 description is front-loaded with purpose and default behavior, and each sentence adds usable information. It runs a bit long with the timestamp sentence, but no sentence is clearly wasteful.

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

Completeness5/5

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

With no output schema, the description still covers returns (source IDs and timestamps), filtering, workflow chaining, plan constraints, and required scope. An agent has enough to call this correctly and know what to do with the results.

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 0%, so the description carries the burden. It explains is_enabled (defaults to enabled, false lists disabled) and platform filtering well, but says nothing about limit or offset, leaving the two pagination parameters entirely undocumented anywhere.

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?

"Discovers global and organization-owned intelligence sources and their IDs for attaching to a policy" gives a specific verb, resource, scope, and purpose. It is clearly distinct from siblings such as list_customer_intel_feeds and manage_policy_intel_sources, which handle different resource types.

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?

It explicitly routes the agent: use list_policies to get the policy ID, then call manage_policy_intel_sources with action=list to inspect attachments or action=attach with the selected source_ids. Default versus disabled listing behavior is also spelled out, so the agent knows which flag to set.

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