T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:39- Finding
Mutable Remote Documentation Is Used to Generate and Execute Invocation Code
- Content
View full analysis
`Synformer_api_doc.md` - `Retrosynthesis Planner` -> `Retrosynthesis Planner_api_doc.md` - `SAScore` -> `SAScore_api_doc.md` The agent MUST: 1. Resolve the selected tool's Markdown file and read it before every invocation. 2. Never invent `provider_name`, `tool_name`, parameter names, enum values, upload-field names, content type, or submission flow from memory. 3. Extract and follow the selected doc section's exact: - Base URL - API endpoint - Content-Type - Authentication header - Tool Name - Method - Parameter table, including required fields and enum values - File-upload instructions and example code 4. Choose the correct section if the selected doc contains multiple tool variants, such as SMILES input vs file upload. 5. Cite the selected Markdown doc as the payload source in summaries. If a user-provided parameter is not present in the selected Markdown doc section, ask for correction or drop it with an explanation. ## Required workflow 1. Determine whether the request matches `Synformer`, `Retrosynthesis Planner`, or `SAScore`. 2. Read the corresponding Markdown file or files from `https://sciminer.tech/tool_api_files/`. 3. Choose the doc section that matches the user's input shape. 4. Collect any missing required parameters from the user. 5. Upload required file inputs exactly as described by the selected Markdown doc and replace loca ...[truncated 3465 chars]- Remediation
View remediation
