Skip to main content
Glama
Sign In

ce-net

by com.ce-net
OverviewDiscussionsAdmin

permission_propose

Ask for a right to be given to an account or to the members of a space.

Input Schema

NameRequiredDescriptionDefault
toYes
ownerNo
scopeNo
spaceNo
reasonNo
capabilityYes
expiry_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Changed1 schema field changed
    • changedInput schema / properties / capability / enum
      Previous value: -[
-  "code.host",
-  "source.write"
-]New value: +[
+  "code.host",
+  "source.write",
+  "compute.submit"
+]
  6. Added
  7. Removed
  8. Added
  9. Removed
  10. Changed7 schema fields changed
    • removedInput schema / properties / capability / properties
      Removed value: -null
    • removedInput schema / properties / expiry_days / properties
      Removed value: -null
    • removedInput schema / properties / owner / properties
      Removed value: -null
    • removedInput schema / properties / reason / properties
      Removed value: -null
    • removedInput schema / properties / scope / properties
      Removed value: -null
    • removedInput schema / properties / space / properties
      Removed value: -null
    • removedInput schema / properties / to / properties
      Removed value: -null
  11. Changed13 schema fields changed
    • addedInput schema / properties / capability / properties
      Added value: +null
    • removedInput schema / properties / expiry_days / description
      Removed value: -"1-365, default 30"
    • addedInput schema / properties / expiry_days / properties
      Added value: +null
    • removedInput schema / properties / owner / description
      Removed value: -"account scope: who grants it (default you); they must hold the right and share a space with you"
    • addedInput schema / properties / owner / properties
      Added value: +null
    • removedInput schema / properties / reason / description
      Removed value: -"why, in a sentence (shown to the owner)"
    • addedInput schema / properties / reason / properties
      Added value: +null
    • removedInput schema / properties / scope / description
      Removed value: -"account (default): one account; space: everyone in the space when approved, while they stay members"
    • addedInput schema / properties / scope / properties
      Added value: +null
    • removedInput schema / properties / space / description
      Removed value: -"a space to post the request and the answer in (default: the space of a space scope)"
    • addedInput schema / properties / space / properties
      Added value: +null
    • removedInput schema / properties / to / description
      Removed value: -"a 16-hex account id, or a space id when scope is space"
    • addedInput schema / properties / to / properties
      Added value: +null
  12. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only, non-idempotent, open-world, non-destructive operation. The phrase 'Ask for' adds useful context that this is a request/proposal rather than an immediate grant, but it does not explain that the request likely becomes pending a decision or what approval flow follows.

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?

The description is a single front-loaded sentence with no wasted words. It is concise, though the phrasing 'Ask for a right to be given' is slightly awkward.

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

Completeness2/5

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

For a seven-parameter mutation tool with no output schema and 0% schema description coverage, the description is too thin. It does not explain the proposal lifecycle, required versus optional parameters, or the meaning of the scope and capability enums.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for seven parameters. The description vaguely maps 'to' to an account or space members and 'capability' to the requested right, but it leaves owner, scope, space, reason, expiry_days, and enum values unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear action (asking/proposing for a right to be granted) and names the two target types: an account or members of a space. It is distinguishable from sibling tools like permission_decide or permission_revoke, though it does not explicitly name alternatives.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as permission_decide, permission_status, or space_grant. The only implied usage is the tautological purpose of asking for a permission.

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

All ce-net toolsInspect
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