Skip to main content
Glama

EaseWeb

by host.easeweb
OverviewDiscussionsAdmin

Get a project

get_project
Read-onlyIdempotent

A project you can see, with its presentations (the ones you can see) in order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe project's slug (its address: /project/<slug>/).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
urlNoThe address people open in a browser.
roleNoowner, edit, view or null.
slugYesThe address of the project: /project/<slug>/.
ownerNo
titleNo
accessNoopen, public or private: inherited by its presentations.
grantsNoWho was given access (the owner sees it).
is_ownerNo
descriptionNo
presentationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / presentations / items / properties / missing_translations / description
      Previous value: -"What is not translated yet into the other languages of the site (add it)."New value: +"What is not translated yet into the other languages of the site (add it): the first ones; \"missing_translations_count\" says how many there are."
    • addedOutput schema / properties / presentations / items / properties / missing_translations_count
      Added value: +{
+  "description": "How many texts are not translated yet.",
+  "type": "integer"
+}
    • addedOutput schema / properties / presentations / items / properties / version
      Added value: +{
+  "description": "Stamp of the content as it is now: give it back as \"base_version\" to change it only if nobody else did meanwhile.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / presentations / items / properties / cover_slide
      Added value: +{
+  "description": "Id of the slide shown as its cover in the lists (null: an uploaded picture, or no slides).",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
  3. Changed6 schema fields changed
    • addedOutput schema / properties / access
      Added value: +{
+  "description": "open, public or private: inherited by its presentations.",
+  "type": "string"
+}
    • addedOutput schema / properties / grants
      Added value: +{
+  "description": "Who was given access (the owner sees it).",
+  "items": {
+    "properties": {
+      "role": {
+        "type": "string"
+      },
+      "since": {
+        "description": "ISO 8601 date and time.",
+        "type": "string"
+      },
+      "user": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / presentations / items / properties / lang
      Added value: +{
+  "description": "The language its texts are written in; \"tr\" holds the others.",
+  "type": "string"
+}
    • addedOutput schema / properties / presentations / items / properties / languages
      Added value: +{
+  "description": "The languages of the site.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / presentations / items / properties / missing_translations
      Added value: +{
+  "description": "What is not translated yet into the other languages of the site (add it).",
+  "items": {
+    "properties": {
+      "block_id": {
+        "type": "integer"
+      },
+      "lang": {
+        "type": "string"
+      },
+      "slide_id": {
+        "type": "integer"
+      },
+      "slide_number": {
+        "type": "integer"
+      },
+      "what": {
+        "description": "title, slide name or block.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / presentations / items / properties / title_tr
      Added value: +{
+  "description": "The same text in the other languages of the site: {\"en\": \"...\"}.",
+  "type": "object"
+}
  4. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds that only visible projects and presentations are returned and that presentations come in order, which is genuine extra context, but it says nothing about error/not-found behavior for a slug the caller cannot see.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the parenthetical '(the ones you can see)' interrupts an already fragmentary sentence and there is no front-loaded statement of what the tool does. Brevity here reads as under-specification rather than efficient structure.

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

Completeness3/5

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

With an output schema present, return values need not be explained, yet the description spends its only sentence on return composition. Annotations cover safety. For a low-complexity single-parameter read the description is minimally sufficient, but it never states the fundamental purpose or when to reach for it.

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?

The single 'project' parameter has 100% schema description coverage, including the slug format '/project/<slug>/'. The description adds no parameter-level meaning, so the schema-only baseline of 3 applies.

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

Purpose3/5

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

The description is a noun phrase with no verb, so the action (fetch/retrieve one project) is only implied by the name 'get_project'. It does add return-content information ('with its presentations ... in order'), which goes slightly beyond a tautology, but it never distinguishes this tool from get_presentation or list_projects.

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 statement of when to use this tool versus get_presentation, list_projects, or get_slide. The phrase 'the ones you can see' hints at a permission scope but is not framed as usage guidance, so an agent gets no routing help.

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

All EaseWeb 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