Meta Council

Create Portfolio Schedule

create_portfolio_schedule

Idempotent

Create an owner-private daily, weekly or monthly portfolio report schedule. Defaults to paused; explicitly enable to start internal captures. Uses the same active-ticket aggregate as manual reports. Optional project_id from project_list limits captures to that owned project; each report retains its own inputs. No email or provider calls. Preserve request_id and exact intent when retrying an uncertain reply. Requires tickets:write.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request_id": "<request_id>",
      "definition": "<definition>"
    },
    "name": "create_portfolio_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`definition`	Yes
`request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / definition / properties / project_id

Added value: +{
+  "anyOf": [
+    {
+      "format": "uuid",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Owned project UUID from project_list. Omit or pass null for a portfolio-wide schedule; project identity is frozen in each capture.",
+  "title": "Project Id"
+}

AddedSep 27, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (which already declare non-read-only, idempotent, non-destructive, closed-world), the description discloses the default paused state, that captures are internal only ('No email or provider calls'), the active-ticket aggregate semantics, and the auth requirement. The retry guidance ('preserve request_id and exact intent') adds practical idempotency context that annotations alone don't convey.

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?

Front-loaded with the core purpose, then progressively narrower details (default state, aggregate semantics, project_id scope, side-effect limits, retry, permission). Dense but each sentence adds information; only slight redundancy in restating project_id scope.

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

Completeness4/5

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

With a nested-object schema, no output schema, and no parameter descriptions, the description supplies default state, side-effect boundaries, permission requirement, and idempotent-retry guidance. It covers enough for correct invocation, though the scheduling fields (hour/minute/timezone) remain undocumented.

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 must carry the load. It explains the meaning of frequency (daily/weekly/monthly), the enabled default (paused), and project_id scope, but the nested fields hour, minute, timezone, weekday, and monthday are left entirely to the schema. Partial compensation only.

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?

The description states a specific verb and resource ('Create an owner-private ... portfolio report schedule') plus the frequency scope (daily/weekly/monthly). This is clearly distinct from siblings such as create_portfolio_snapshot, create_portfolio_report_share, and update_portfolio_schedule.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete operating context: schedules default to paused and must be explicitly enabled to start captures, and project_id should come from project_list. It also states the prerequisite ('Requires tickets:write'). It does not explicitly contrast with update_portfolio_schedule or list_portfolio_schedules, so it stops short of full when/when-not routing.

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

All Meta Council tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?