Docs

Tools: platform

7 tool(s) in this category.

prompts.system.getting_started

Getting Started Prompt

Use when a caller asks how to start or wants an overview of the 3 Amdahl MCP tools. Returns the full getting-started skill content (tool map, recommended workflow, substrate mechanics, tips) as a single user message.

  • HTTP: (not exposed as REST)
  • Required scopes: prompts:list
  • Required role: viewer
  • Stability: stable
  • Version: 1.0
  • Tags: prompt, system, onboarding

Input

No structured input.

prompts.system.research_playbook

Research Playbook Prompt

Use when the caller asks how to investigate a topic end to end using the 3-tool surface. Returns the full research playbook (routing rule, recommended flow, substrate accumulation, intent-driven lookups, parallel work, examples) as a single user message.

  • HTTP: (not exposed as REST)
  • Required scopes: prompts:list
  • Required role: viewer
  • Stability: stable
  • Version: 1.0
  • Tags: prompt, system, research

Input

No structured input.

read_resource

Read Resource

Read any resource by URI. URIs follow <scheme>://<path>[?query]. Schemes: artifact, conversation, agent_run, agent_profile, context, context_entry, knowledge_base, webhook, data, content. Examples: artifact://abc-123 returns one artifact; context://summary grounds you in the business; data://schema is the data inventory. Use when you need to read existing state. See "Available resources" in your system prompt for the full list.

  • HTTP: GET /resources
  • Required scopes: artifacts:read
  • Required role: viewer
  • Stability: stable
  • Version: 1.0
  • Tags: read-only, meta

Input

FieldTypeRequiredDescription
uristringyesThe resource URI to read. Example: artifact://abc-123, artifact://list?type=content_piece, conversation://list, context://summary, context_entry://list?type_prefix=brand., knowledge_base://<id>, webhook://<id>/deliveries, data://schema, content://session/<id>, agent_profile://list.

system.list_prompts

List Prompts

Enumerate author-blessed prompt templates the current caller can invoke. Each entry carries a name, description, optional scheme (namespace prefix), and optional argsSchema. Use when the user asks "what can I do" or wants to discover available prompts, filter commands, or actions for a domain. Pass scheme to narrow to one family (e.g. briefing). Call use_prompt with one of the returned names to invoke it.

  • HTTP: GET /prompts
  • Required scopes: prompts:list
  • Required role: viewer
  • Stability: stable
  • Version: 1.0
  • Tags: read-only, meta, prompts

Input

FieldTypeRequiredDescription
schemestringnoOptional namespace prefix. Names look like <scheme>/<leaf> (briefing/account). Pass scheme="briefing" to return only briefing-family prompts.

system.use_prompt

Use Prompt

Invoke an author-blessed prompt template by name. The response is a messages array (role + content pairs) you can fold into subsequent reasoning, like expert guidance assembled from business context rather than a final answer. Use when you want to apply a saved prompt template for a briefing, battlecard, or similar task. Call list_prompts first to discover available names.

  • HTTP: POST /prompts/use
  • Required scopes: prompts:use
  • Required role: viewer
  • Stability: stable
  • Version: 1.0
  • Tags: meta, prompts

Input

FieldTypeRequiredDescription
namestringyesGlobally unique prompt slug returned by list_prompts (e.g. briefing/account).
argumentsobjectnoOptional arguments for the prompt, validated against the prompt's declared argsSchema. Omit for prompts that take no arguments.

webhooks.test_fire

Test Fire Webhook

Fire a signed test delivery at a webhook destination and return the captured response. Use when verifying connectivity to a new subscription, debugging signature handling, or checking the receiver is up. Signed with the production HMAC-SHA256 scheme; an X-Webhook-Test: true header lets receivers no-op safely. One attempt only, no retries. Does not affect failure_count or last_delivery_at aggregates.

  • HTTP: POST /webhooks/:id/test
  • Required scopes: webhooks:write
  • Required role: admin
  • Stability: stable
  • Version: 1.0
  • Tags: destructive, external_http, webhooks

Input

FieldTypeRequiredDescription
idstringyesUUID of the webhook to fire.
eventstringnoEvent name for the test payload. Defaults to "test.ping".
payloadobjectnoOptional payload body. Defaults to { test: true, timestamp: <iso-now> } when omitted.

webhooks.write

Write Webhook

Create, update, or delete a webhook subscription. Use when registering a new destination, changing URL / event list / description / active, or removing a subscription. action="create" returns the secret once — record it. action="update" requires id and at least one patch field. action="delete" requires id. Reads use the webhook:// resource family.

  • HTTP: POST /webhooks/write
  • Required scopes: webhooks:write
  • Required role: admin
  • Stability: stable
  • Version: 1.0
  • Tags: write, webhooks

Input

FieldTypeRequiredDescription
action`enum("create""update""delete")`
idstringno
urlstringno
events`array<enum("artifact.created""artifact.updated""artifact.status_changed"
secretstringnoOptional HMAC secret for create. Must be >= 16 chars. Stored encrypted.
descriptionstringno
activebooleanno