Pyrfor Engine — open runtime core: Memory, Skills, Provider Router, MCP-server, Heartbeat, Tool Engine
21 tools with schemas present but significant quality gaps. Most tools have descriptions (good), but many descriptions are generic or under-optimized for LLM selection. Parameter descriptions are sparse or missing entirely. No tool annotations (readOnlyHint/destructiveHint). Output schemas are not documented. Error handling guidance is absent. Naming is generally clear (verb_noun pattern), but parameter naming lacks consistency (e.g., 'projectId' vs 'project_id'). No evidence of idempotency hints or confirmation patterns for destructive operations.
Create a project expense. Use when the user asks to record spending, cost, payment, or fact.
Create a material movement record for inventory tracking.
Create a new project
Register a new project risk. Use when the user mentions a problem, threat, blocker, or concern.
Create a new task in a project. Use when the user asks to add, create, or schedule a task.
Generate a morning/status briefing for the user. Use when user asks for a brief, summary, or 'what happened'.
Get expense and budget summary for one project or across active projects.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLM cannot distinguish safe read-only tools from destructive writes without explicit hints. All WRITE tools (create_*, update_*, sync_1c) lack destructiveHint annotation.
Output schemas not documented. Tools return data but LLM has no schema to understand response structure. Prevents downstream tool chaining and forces LLM to infer field names.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Get the critical path for project scheduling.
Get overall dashboard analytics and KPIs
Get health report for a specific project
Get project status
Get a summary of a project including task counts, risks, and progress. Use for status questions.
Get resource load and allocation for project scheduling.
Get workload distribution across team members
List equipment inventory items with optional filters.
List all projects
List tasks with optional filters. Use when user asks about tasks, what needs to be done, what's overdue.
Synchronize data with 1C accounting system.
Update project budget
Update project progress
Update an existing task (change status, priority, due date, etc). Use when user asks to mark done, change priority, reschedule.
Sparse parameter descriptions. Many parameters lack descriptions or have minimal guidance (e.g., 'Optional project ID to filter by' for get_team_workload). LLM cannot determine when/how to use optional params.
No error handling guidance. Tools provide no recovery hints (e.g., 'If project not found, call list_projects() first'). Agents cannot self-correct on failures.
sync_1c tool has minimal description ('Synchronize data with 1C accounting system') and empty input schema. Unclear what this does, when to call it, or what it returns. Likely inferred tool definition.