# PlatPhorm MCP Tool-Calling Skill

Use this skill when a task may be served by the PlatPhormNews capability network.

## Endpoint

- MCP Streamable HTTP: https://mcp.platphormnews.com/mcp
- Protocol version: 2026-07-28
- Tool recommender: https://mcp.platphormnews.com/api/v1/model/recommend-tools

## Fast path

1. Describe the user task to GET /api/v1/model/recommend-tools?task=<plain English>&limit=5.
2. Choose a recommendation using its title, match reasons, owner, status, authorization, and input schema.
3. Fill only schema-supported arguments.
4. Invoke the recommendation's canonical name with JSON-RPC tools/call at its returned endpoint.
5. Treat the response as execution evidence only when the tool returns a concrete successful result.

## Call shape

~~~json
{"jsonrpc":"2.0","id":"call-1","method":"tools/call","params":{"name":"<canonical-name>","arguments":{}}}
~~~

## Rules

- Human titles and aliases are for reading and search. Never invoke an alias.
- Public introspection and public-safe reads need no credential.
- Mutations, delegation, proxying, sync, tests, reporting, and administration require PLATPHORM_API_KEY supplied server-side.
- Follow nextCursor for MCP lists. Do not retain the entire network catalog unless the task requires it.
- A federated listing, candidate, preview, or degraded record does not prove downstream execution.
- Preserve JSON-RPC IDs and W3C traceparent when provided. Never place credentials in prompts, traces, logs, or public artifacts.
- If recommendation evidence is stale or unavailable, use bounded tools/list, inspect the exact schema, and report the limitation.